npm why (who installs this package)
MCP serverMCP server that explains why an npm package is in your lockfile and who pulls it in
Runs locally- 2 tools
- Open source
- Developer tools
MCP server that explains why an npm package is in your lockfile and who pulls it in
Runs locallynpm registry intelligence, security audits and publish-side writes without the 2FA prompt
Runs locallyMCP server that reports which file Node loads for a given import or require, and why
Runs locallyCheck how long ago a package version was published before an agent adds it
Runs locallyChecks npm and PyPI package names against live registries before you install
Not checked yetLocal read-only acceptance report on what an AI coding change touched and checked
Runs locallyMCP server that shows which files docker build sends and which .dockerignore line decides
Runs locallyRead-only npm preflight: reviews what install scripts do before packages run
Runs locallyScans lockfiles for known vulnerabilities and risky licences, with re-scan alerts
Not checked yetMCP server that answers whether git ignores a path and which .gitignore line decides
Runs locallyLook up malicious and vulnerable npm packages, free and without an API key
Not checked yetLive npm and UNPKG lookups, import map checks and malware or CVE verdicts for agents
Not checked yetThe closest alternatives to npm pack checker (what npm publish ships) are npm why (who installs this package), npm Registry MCP Server, package.json exports resolver (which file Node loads), unripe and Notary.
Yes. npm why (who installs this package), npm Registry MCP Server, package.json exports resolver (which file Node loads) have a free or open-source option.