A pre-publish scanner that strips source maps, secrets, and internal code from npm packages before they ship to the registry
Anthropic accidentally shipped 512K lines of Claude Code source code via an npm source map file that was never meant to be public. This happens constantly because .npmignore and package.json files fields are easy to misconfigure. The repo got 100K+ stars in days as people reversed the entire codebase. This tool scans your npm package before publish, catches source maps, leaked environment variables, internal documentation, and accidentally included files, then blocks the publish until you fix it.
Demand Breakdown
Social Proof 5 sources
Gap Assessment
3 tools exist (npm-packlist, Socket.dev, Secretlint) but gaps remain: No content scanning, no secret detection, no source map analysis, just file listing; Post-publish only, no pre-publish prevention, no source map deep analysis, consumer-side not publisher-side.
Features4 agent-ready prompts
Competitive LandscapeFREE
| Product | Does | Missing |
|---|---|---|
| npm-packlist | Lists files that npm pack would include | No content scanning, no secret detection, no source map analysis, just file listing |
| Socket.dev | Scans npm packages for supply chain attacks post-publish | Post-publish only, no pre-publish prevention, no source map deep analysis, consumer-side not publisher-side |
| Secretlint | Scans files for hardcoded secrets using pattern matching | General-purpose, not npm-publish-aware, no source map analysis, no package.json files field checking |
Notable VoicesFREE
Leads40BUILDER
Sign in to unlock full access.