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.3101 npm4MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to check npm packages, GitHub Action refs, and remote scripts before execution, returning deterministic ALLOW/DENY/REVIEW verdicts with evidence and a re-checkable manifest.MIT
- 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.86 npm8MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.MIT
- 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.2 npmMIT
TDQS
Scored across 7 tools
The three check tools (check_package, check_upgrade, check_manifest) target related but distinct contexts (single install, version bump, full manifest), and the descriptions explicitly state when to call each. review_install_scripts, safe_version, diff_release, and replay_incident are clearly separate purposes, though the check trio could still be confused at a glance.
All tools use a consistent bouncer_ prefix with snake_case and mostly verb_noun form (check_package, diff_release, replay_incident, review_install_scripts). safe_version is a minor deviation lacking a verb, but the overall pattern is predictable.
Seven tools is well-scoped for a dependency-security verdict server, with each tool earning its place across pre-install checks, version selection, evidence, and install-script review.
The surface covers the core lifecycle: checking packages, upgrades, and manifests, plus safe-version selection, raw diffs, and install-script review. It lacks obvious config/allowlist management or bulk/CI scan operations, but the primary agent workflows are covered with no hard dead ends.