If you find a security issue in mojo-postgres — particularly anything that could allow SQL injection through the wrapper, memory corruption via the FFI layer, or credential leakage through misconfigured TLS — please do not open a public issue.
Instead, use GitHub's private vulnerability reporting:
- Go to https://github.com/dvirarad/mojo-postgres/security/advisories/new
- Describe the issue with a minimal repro.
- Expect an acknowledgment within 72 hours.
For non-security bugs, regular issues are the right place.
In scope:
- Anything inside
src/postgres/that talks tolibpq. - Examples that mishandle untrusted input.
Out of scope:
- Vulnerabilities in
libpq/ PostgreSQL itself — report those upstream at https://www.postgresql.org/support/security/. - Vulnerabilities in user code that happens to import
mojo-postgres.