pkgguard
Related Servers
Alternatives to pkgguard
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents and users to check npm, PyPI, and crates.io packages before installation for hallucinated names, malware, exact-version CVEs, and signs of compromised releases, with MCP tools for package checks and lockfile audits.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables developers and AI coding agents to vet npm packages before installation by checking existence, lookalike names, package age, install scripts, maintainers, downloads, and advisories, returning GO, RISKY, FAKE, or MISSING. It also scans a project's package.json for worst-first dependency verdicts and can run as a CLI or stdio MCP server.MIT
- AlicenseAqualityDmaintenanceActs 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.731 npm5MIT
- AlicenseNot gradedqualityDmaintenanceValidates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.60 npmAGPL 3.0
- AlicenseAqualityBmaintenanceEnables 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.352 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.4 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of misselection or overlap. The single tool's purpose—authorizing a generated install command—is clearly distinct and unambiguous.
The lone name 'authorize_install_command' uses a clean snake_case verb_noun pattern. There are no other tools to conflict with or deviate from this convention.
A single tool is borderline thin even for a narrow gate-focused server. A minimal surface like this can work as a focused approval hook, but it leaves little room for related operations.
The core authorize action is covered, but there is no way to inspect policy, retrieve prior decisions, or explain a denial. Agents hitting a blocked command have no follow-up path, which is a notable but workable gap for such a narrow domain.