Support and Security

Support and security

Use GitHub Discussions for configuration help, architecture questions, and ideas that still need exploration.

Use GitHub Issues for reproducible defects and concrete enhancements. Include the smallest configuration and query needed to reproduce the behavior, along with current WordPress, PHP, database, and LudicrousDB versions.

Report suspected vulnerabilities through private vulnerability reporting. Do not disclose a vulnerability publicly before maintainers have had a reasonable opportunity to investigate and coordinate a fix.

Never post credentials

Public GitHub content is visible indefinitely and may be indexed or copied. Remove database passwords, usernames, hosts, IP addresses, private domains, tokens, private keys, connection strings, customer data, and backups before posting.

If a secret is exposed, rotate it immediately. Editing or deleting the public text is still worthwhile, but it cannot make the old value safe again.

See Troubleshooting for the details that make a report useful without revealing sensitive information.