Dep Bouncer
Related Servers
Alternatives to Dep Bouncer
No user-submitted related servers found.
Related Servers
- 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.361 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to verify, compare, and safely upgrade npm packages by scoring packages from public signals and sandboxed co-installation, detecting breaking API surface changes, and rewriting code that upgrades break.29 npm8MIT
- 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
- AlicenseAqualityAmaintenanceVerifies npm packages for security risks before installation, checking advisories, install scripts, typosquatting, and other factors, providing safe/block verdicts.1550 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.5MIT
- AlicenseNot gradedqualityCmaintenanceAudits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.MIT
TDQS
Scored across 7 tools
Each tool has a distinct entry point (single new package, version bump, whole manifest, safe-version selection, install-script approval, raw diff, incident demo), and descriptions clarify when to use each. However, bouncer_check_package, bouncer_check_upgrade, bouncer_diff_release and bouncer_check_manifest all revolve around the same compare-a-release-to-its-history logic, so an agent may hesitate between them for a given situation.
All seven tools share the bouncer_ prefix and a consistent snake_case verb_noun pattern (check_package, check_upgrade, review_install_scripts, check_manifest, diff_release, replay_incident). bouncer_safe_version is the only slight deviation but remains readable and predictable.
Seven tools is well within the ideal 3-15 range and each one maps to a concrete workflow (vet a package, vet a bump, vet a manifest, pick a safe version, approve scripts, inspect a diff, demo an incident). No tool feels redundant or filler.
The surface covers the core dependency-vetting lifecycle: pre-install checks, upgrade checks, bulk manifest scanning, safe-version fallback, install-script approval review, diff evidence, and incident replay. Minor gaps exist around policy configuration/allowlisting and lockfile- or CI-level enforcement, but agents can work around these for the stated purpose.