# @guardbee/mcp-dependency-auditor

CVE scanning for npm/pip/cargo dependencies via OSV

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.4
- **Author:** io.github.4hmetuyar
- **License:** MIT
- **npm:** @guardbee/mcp-dependency-auditor
- **Source:** https://github.com/GuardBee/guardbee-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-10T22:28:15.611Z
- **Version scanned:** 0.2.4
- **CVEs:** none found by OSV at scan time

## Tools

4 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `audit_npm` — Audit npm dependencies from a package.json (and optionally package-lock.json) for known CVEs using the OSV database
- `audit_pip` — Audit Python dependencies from requirements.txt or pyproject.toml for known CVEs using the OSV database
- `audit_package` — Audit a single package by name, version, and ecosystem
- `audit_directory` — Auto-detect and audit npm and pip manifests (package.json, requirements.txt, pyproject.toml) in a directory

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-dependency-auditor\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@guardbee/mcp-dependency-auditor\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-dependency-auditor
- Install plan: https://forgeregistry.com/api/v1/packages/%40guardbee%2Fmcp-dependency-auditor/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40guardbee%2Fmcp-dependency-auditor
- HTML page: https://forgeregistry.com/registry/%40guardbee%2Fmcp-dependency-auditor
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.