| Version | Supported |
|---|---|
| 1.4.x | Yes |
| < 1.4 | No |
Please report vulnerabilities privately through GitHub: open the repository's Security tab and use "Report a vulnerability" (private vulnerability reporting). Do not open a public issue for a security problem.
Include, where you can:
- the affected version and configuration (your
babelgate.yaml, orTARGET_APIin env-only mode, with keys removed) and the client you used (Claude Code, Codex CLI, an SDK, …), - steps to reproduce, and
- the impact you believe the issue has.
Never include API keys — yours or anyone else's — in a report.
You can expect an acknowledgement within a few days. If the report is accepted, a fix will be prepared privately and released before details are made public.
Every v* tag triggers .github/workflows/release.yml, which builds,
pushes and signs the GHCR image automatically. Publishing to npm and
creating the GitHub release are done by the maintainer by hand, so the
container image is the only artifact with a CI-generated attestation:
-
Signed container image. The GHCR image is signed keyless by cosign in the same workflow run. Verify a tag (or a digest,
ghcr.io/dorrabbkhan/babelgate@sha256:…) with:cosign verify ghcr.io/dorrabbkhan/babelgate:<version> \ --certificate-identity-regexp '^https://github\.com/dorrabbkhan/babelgate/\.github/workflows/release\.yml@refs/tags/v.*$' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com
-
npm registry signatures. The npm tarball is published by hand, so it carries no provenance bundle (provenance can only be minted by a trusted CI builder). npm does add a registry signature to every package it serves (https://docs.npmjs.com/about-registry-signatures); check
babelgate's — and every dependency's — with:npm audit signatures
-
SBOM (manual). The maintainer generates a CycloneDX SBOM of the runtime dependencies (devDependencies excluded) and attaches it to each GitHub release as
babelgate-<version>.cdx.json:npm ci && npm sbom --sbom-format cyclonedx --omit dev > babelgate-<version>.cdx.json
The "Runtime dependencies: " line in the release notes comes from:
npm ls --omit=dev --all --parseable | tail -n +2 | wc -l
babelgateforwards upstream provider keys stored in its environment — treat.envand any process dump as secret material.- Client access is gated by
PROXY_API_KEYwhen set; without it the proxy is open — run it only on trusted networks. - The proxy never logs prompt bodies, completions, or keys. Bodies are kept
only in an in-memory ring for the
/uiInspector, and on disk only withLOG_BODIES=true. The/uianswers only local clients unlessUI_ALLOW_REMOTEis set orPROXY_API_KEYis presented. If you find a path where one leaks into logs or error messages, that is a bug — report it privately as above.