| Version | Supported |
|---|---|
| Latest minor (currently 1.0.x) | Security + bug fixes |
| Previous minor | Security + bug fixes |
| Older | Security fixes only for 90 days after supersession |
Please report suspected vulnerabilities privately via GitHub Security Advisories.
Do not open a public issue for a suspected vulnerability.
We follow a 90-day coordinated disclosure policy:
- We acknowledge reports within 3 business days.
- We investigate and confirm within 14 days.
- We target a fix within 60 days of confirmation.
- We publish an advisory and release the fix by day 90 at the latest.
Longer windows may be negotiated for complex issues.
This project is a local emulator intended for development and testing. It does not verify authentication and accepts any credentials. That is by design for the emulator's use case; it is not a vulnerability in the emulator itself.
Vulnerabilities in scope include:
- Remote code execution via crafted SQL or proto payloads.
- Sandbox escapes in the JavaScript UDF runtime.
- Path traversal in load / extract job file handling.
- Denial of service via unbounded resource consumption.
- Supply-chain concerns in our published artifacts.
Out of scope:
- Lack of authentication enforcement (by design — use in local development environments only).
- Issues in third-party dependencies not reachable from emulator code.
- Container images published to
ghcr.io/jjviscomi/bqemulatorare signed with cosign and include SLSA provenance attestations. - Wheels published to PyPI include sigstore attestations via Trusted Publishing.
Verification instructions live in docs/architecture/contributing/release-process.md.