pkgproof
Related Servers
Alternatives to pkgproof
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAudits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.MIT
- AlicenseAqualityBmaintenanceEnables checking packages across npm, PyPI, Go, Maven, Cargo, NuGet, and RubyGems for existence, deprecation, known vulnerabilities, and license issues before installation, providing verdicts like does_not_exist, risky, verify, or ok.31MIT
- AlicenseAqualityAmaintenanceEnables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.323 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceAudits your package-lock.json for supply-chain attacks before install. Cross-checks every resolved entry against the live npm registry to detect integrity mismatches, new install scripts, and other malicious signals.MIT
- AlicenseAqualityDmaintenanceVerifies npm package names for safety, detecting typosquats and nonexistent packages before your coding agent installs them.28 npmMIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another operation. Its purpose (verify an npm/PyPI package before install) is stated precisely, so misselection is not a concern.
verify_package uses a clean, predictable verb_noun snake_case pattern. A one-tool surface cannot exhibit convention mixing, so consistency is trivially perfect.
One tool is thin for a server, even though the tool deliberately aggregates nine checks and four verdicts into a single call. It is defensible as a focused single-purpose service, but it sits at the borderline of feeling under-scoped.
The single call covers the core verification lifecycle well: advisories, install scripts, typosquat/combosquat, scope, repository, and release diffing, with labelled fact/heuristic reasoning. Minor gaps remain (no batch/multi-package verification, no result caching or history retrieval), but agents can work around them.