pkgtruth
Related Servers
Alternatives to pkgtruth
No user-submitted related servers found.
Related Servers
- 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.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceAudits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.MIT
- AlicenseAqualityDmaintenanceDependency security & health auditing for AI agents with no account or API key required.22MIT
- AlicenseAqualityBmaintenanceVerifies npm packages for security risks before installation, checking advisories, install scripts, typosquatting, and other factors, providing safe/block verdicts.1235 npmApache 2.0
- AlicenseAqualityFmaintenanceActs as a security checkpoint for AI coding agents by intercepting package installations to verify existence, check against CVE databases, and block vulnerable or hallucinated dependencies before they reach your codebase. Provides seven security tools including pre-install gates, full project audits, safe version recommendations, and deep transitive dependency scanning for npm and PyPI packages.746 npm4MIT

EVIDIQ Lineageofficial
AlicenseNot gradedqualityBmaintenanceDeterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.1MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct scope: single package, multiple packages, and install command parsing. No overlap in purpose, and descriptions explicitly differentiate when to use each, eliminating ambiguity for the agent.
All three tools follow the consistent 'check_' + object pattern: check_package, check_dependencies, check_install_command. The verb is uniform and the object clearly indicates the target, making the naming predictable and intuitive.
With 3 tools, the server is tightly scoped to package verification and covers the essential granularity levels (single, bulk, command). Each tool serves a distinct need without redundancy, and the small count feels intentional rather than incomplete.
The tool surface covers the full workflow of package verification: checking individual packages, checking dependency lists before manifest creation, and validating install commands. The descriptions also handle edge cases like bare installs and lockfile usage, indicating thoughtful coverage with no obvious gaps.