package-guard-mcp

Audit a set of npm or PyPI dependencies in one call. Give it a list of names, or the text of a package.json (its dependencies and devDependencies), or the text of a requirements.txt. Returns a per-package report (exists, vulns, malicious, deprecated, verdict, flags) and a summary. Direct entries only: no lockfile is parsed and no transitive dependency is resolved, so this is not a full-tree audit and a vulnerable grandchild dependency will not appear. First 40 names, the rest are dropped and truncated is set. A version range is reduced to the digits inside it, so ^4.17.20 is checked as 4.17.20 and the real resolved version may differ. When the batch OSV call fails, every package reports vulns=null with vulns_checked=false rather than a reassuring zero. Network: needs registry.npmjs.org, pypi.org, api.osv.dev.

Known vulnerabilities and malware advisories for a package, optionally for one version, from the OSV.dev database. This is the one tool here that is correct for all seven ecosystems it accepts (npm, PyPI, Go, crates.io, RubyGems, Maven, NuGet), because it queries OSV directly and never touches a registry. It therefore cannot tell you whether the package exists, who publishes it, or whether it is maintained. An empty list means OSV held nothing for that name and version, not that the package is safe: OSV only knows what has been reported. A failed lookup returns an error and never an empty list. Network: needs api.osv.dev.

Registry metadata for an npm or PyPI package: latest version, first and last publish dates, age, weekly downloads, deprecation, license, repository and description. Use it to judge whether a dependency is maintained. It makes no security judgement and runs no vulnerability lookup. Weekly downloads come from api.npmjs.org or pypistats.org and the field is simply absent when those are unavailable, so a missing weekly_downloads is not a zero. License and repository are whatever the publisher declared, unverified. Network: needs registry.npmjs.org, pypi.org.

Generate lookalike names around an npm or PyPI package and report which ones are actually registered and which look recent enough to be suspicious. The variants are heuristic and ASCII only: single-character deletions, adjacent transpositions, doubled letters, the swaps l/1, o/0, rn/m, -/_, ./-, i/l and s/z, and the name with every hyphen or underscore dropped. Up to 20 variants, no Unicode homoglyphs, no prefix or suffix squats such as name-js or python-name, so an empty result is not evidence that nobody is squatting the name. "suspicious" means only that the variant is registered and is either under a year old or has no creation date, which catches new squats and also flags legitimate new packages. Registration is not evidence of malice: nothing here inspects what a variant contains. Network: needs registry.npmjs.org, pypi.org.

The pre-install guard for npm and PyPI. Call it before installing or recommending a package. Returns safe, caution or danger from deterministic checks: is the name registered, does OSV hold vulnerability or malware advisories for it, how old is it, weekly downloads, deprecation, license. If the name is not in the registry, likely_hallucination is set and npm names come with a "did you mean" list (PyPI names get an empty list). That flag means "not in this registry" and cannot tell an AI-invented name from a typo, a rename, or a package that only lives in a private registry. The slopsquat and typosquat score is a heuristic, not a finding: it adds up age under 90 days, under 50 weekly downloads, and a name within 2 edits of an npm search hit, so it both false-alarms on new legitimate packages and misses well-aged malicious ones. Package contents are never downloaded or analysed, so a malicious package with no OSV advisory reads as safe here. vulnerabilities.checked=false with count=null means the OSV lookup failed and the package was NOT checked: treat that as unknown, not as clean. Network: needs registry.npmjs.org, pypi.org, api.osv.dev.