One packaging mistake can ship your entire codebase.
Source maps, .env files, internal docs and debug builds get bundled into published packages every day. ReleaseShield inspects the final artifact in CI and blocks the release before it leaks.
Free, no login. We scan the exact artifact a user would install, not your git repo.
Scan what you ship, not just what you commit
Build
Your pipeline runs npm pack, python -m build or docker build as usual.
Unpack & inspect
ReleaseShield opens the final artifact, exactly what users will download, and scans every file.
Block or ship
Critical findings fail the job before publish. Clean builds ship, with a report in the job summary.
# .github/workflows/release.yml
- uses: actions/checkout@v4
- run: npm ci
- uses: my2ctyw8h6-hash/release-shield@v1
with:
fail-on: critical
token: ${{ secrets.RELEASESHIELD_TOKEN }}
- run: npm publish
# …or anywhere:
curl -fsSLo releaseshield.mjs https://release-shield-app.vercel.app/releaseshield.mjs
node releaseshield.mjs scan --fail-on criticalWhat ReleaseShield catches
Source maps
*.map files, especially ones with sourcesContent that rebuild your full original code.
.env & credentials
.env, .npmrc auth tokens, .pypirc, service-account JSON, private keys.
Hard-coded secrets
AWS, Stripe, GitHub, npm, Slack, OpenAI, Anthropic, Google and DB URLs.
Internal code & docs
Roadmaps, internal/ folders, unreleased features, .git metadata.
Debug artifacts
Logs, coverage output, database dumps, backups and editor files.
Infra fingerprints
Internal hostnames, private IPs, Terraform state and CI config.
Simple pricing for teams that ship
A single leaked source map can cost more than a decade of ReleaseShield.
Spot-check any public npm package or tarball.
- Unlimited one-off scans
- Source maps, .env, keys & tokens
- No login required
For small teams shipping a few packages
- Every release scanned before publish, not just once
- Up to 5 packages / repos
- GitHub Action + CLI for GitLab, CircleCI & any CI
- npm, PyPI and Docker artifact scanning
- Fail-the-build on critical findings
- Slack alerts on critical & high findings
- JSON, SARIF & Markdown reports
- 24/7 tarball monitoring: we inspect every new version you publish to npm and alert you if a secret or .env slips in Coming soon
- Hosted scan history Coming soon
For teams with many packages & release pipelines
- Unlimited packages / repos
- Everything in Standard, plus:
- Private npm registries (GitHub Packages, Artifactory & more)
- Custom policies: ignore files & rules per repo
- Diff vs. previous release: new files flagged
- Priority support
- 24/7 tarball monitoring: we inspect every new version you publish to npm and alert you if a secret or .env slips in Coming soon
- Audit log & SOC 2 evidence export Coming soon
- Hosted scan history Coming soon
Secure checkout by Stripe · Cancel anytime · Prices in USD
FAQ
How is this different from git secret scanners?
Secret scanners look at your repository. Leaks happen in the build output: a bundler emits source maps, a stray .env sneaks into the package, a debug build is published. ReleaseShield inspects the artifact itself.
Do you store my code?
No. The free checker scans artifacts in memory and discards them. The CLI and GitHub Action run entirely on your own CI runner, so your code and scan results never reach our servers.
Which registries are supported?
npm tarballs, PyPI wheels and sdists, and Docker images (via docker save, so images pulled from any registry work). Pro can also fetch packages from private npm registries such as GitHub Packages and Artifactory.
Can I cancel anytime?
Yes. Plans are month-to-month and billed through Stripe. Reply to any Stripe receipt to cancel and you won't be charged again.