Claude Skill

dependency-check

Audit project dependencies for known-vulnerable versions and risky pinning. Parses requirements.txt and package.json, matches a bundled offline advisory DB, optionally queries OSV.dev live, and warns about unpinned versions. Use when the user asks to "check dependencies for vulne

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download NovaCode37-claude-security-skills-skills_dependency-check-2b3ed4a.zip · 8 KB
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/NovaCode37/claude-security-skills/tree/main/skills/dependency-check
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install novacode37-claude-security-skills@llmmart
Git git clone https://github.com/NovaCode37/claude-security-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole novacode37/claude-security-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Dependency Check

Scans Python (requirements.txt) and npm (package.json) manifests for known-vulnerable versions and supply-chain risks. Offline by default — it ships a bundled advisory database so it runs in air-gapped CI — with an optional live OSV.dev lookup. Pure standard library.

When to use this skill

  • "Are any of my dependencies vulnerable?"
  • "Audit requirements.txt / package.json."
  • "Check for vulnerable / outdated packages before release."

What it reports

  • Known vulnerabilities — version matches against the bundled advisory DB (or OSV.dev with --online), with CVE/ID, severity and summary.
  • Unpinned dependencies — ranges (^, ~, >=) or missing pins that make builds non-reproducible and widen supply-chain exposure.

How to run it

# Offline scan (bundled advisory DB)
python skills/dependency-check/checker.py requirements.txt
python skills/dependency-check/checker.py package.json

# Scan a directory (auto-discovers both manifest types)
python skills/dependency-check/checker.py .

# Live advisory lookup via OSV.dev
python skills/dependency-check/checker.py requirements.txt --online

# JSON output
python skills/dependency-check/checker.py . --json

# Only report MEDIUM or higher findings (unpinned warnings are LOW)
python skills/dependency-check/checker.py . --min-severity medium

Exit codes: 0 clean · 1 findings reported · 2 no manifest / usage error. Unpinned dependencies are reported, so they fail the build too; suppress them with --no-unpinned, or raise --min-severity to filter advisory findings out of both the report and the exit code.

Recommended workflow for Claude

  1. Run offline first for a fast baseline, then --online for full coverage if the user has network access.
  2. For each vulnerable package, recommend the minimum fixed version and note breaking-change risk.
  3. Encourage exact pins (== / lockfiles) for reproducible, auditable builds.

Note

The bundled DB is intentionally small (well-known historical CVEs) so the tool is self-contained and testable. For comprehensive coverage use --online (OSV.dev) or integrate a dedicated scanner; treat the offline DB as a fast first pass.

Files (claude-security-skills)
  • tests
    • test_checker.py 10.7 KB
      Loading…
  • checker.py 14.2 KB
    Loading…
  • SKILL.md 2.7 KB
    ---
    name: dependency-check
    description: >-
      Audit project dependencies for known-vulnerable versions and risky pinning.
      Parses requirements.txt and package.json, matches a bundled offline advisory
      DB, optionally queries OSV.dev live, and warns about unpinned versions. Use
      when the user asks to "check dependencies for vulnerabilities", "audit my
      requirements.txt / package.json", "scan for vulnerable packages", or "is my
      dependency tree secure".
    license: MIT
    ---
    
    # Dependency Check
    
    Scans Python (`requirements.txt`) and npm (`package.json`) manifests for
    known-vulnerable versions and supply-chain risks. **Offline by default** — it
    ships a bundled advisory database so it runs in air-gapped CI — with an optional
    live OSV.dev lookup. Pure standard library.
    
    ## When to use this skill
    
    - "Are any of my dependencies vulnerable?"
    - "Audit requirements.txt / package.json."
    - "Check for vulnerable / outdated packages before release."
    
    ## What it reports
    
    - **Known vulnerabilities** — version matches against the bundled advisory DB
      (or OSV.dev with `--online`), with CVE/ID, severity and summary.
    - **Unpinned dependencies** — ranges (`^`, `~`, `>=`) or missing pins that make
      builds non-reproducible and widen supply-chain exposure.
    
    ## How to run it
    
    ```bash
    # Offline scan (bundled advisory DB)
    python skills/dependency-check/checker.py requirements.txt
    python skills/dependency-check/checker.py package.json
    
    # Scan a directory (auto-discovers both manifest types)
    python skills/dependency-check/checker.py .
    
    # Live advisory lookup via OSV.dev
    python skills/dependency-check/checker.py requirements.txt --online
    
    # JSON output
    python skills/dependency-check/checker.py . --json
    
    # Only report MEDIUM or higher findings (unpinned warnings are LOW)
    python skills/dependency-check/checker.py . --min-severity medium
    ```
    
    **Exit codes:** `0` clean · `1` findings reported · `2` no manifest / usage
    error. Unpinned dependencies are reported, so they fail the build too; suppress
    them with `--no-unpinned`, or raise `--min-severity` to filter advisory
    findings out of both the report and the exit code.
    
    ## Recommended workflow for Claude
    
    1. Run offline first for a fast baseline, then `--online` for full coverage if
       the user has network access.
    2. For each vulnerable package, recommend the **minimum fixed version** and
       note breaking-change risk.
    3. Encourage exact pins (`==` / lockfiles) for reproducible, auditable builds.
    
    ## Note
    
    The bundled DB is intentionally small (well-known historical CVEs) so the tool
    is self-contained and testable. For comprehensive coverage use `--online`
    (OSV.dev) or integrate a dedicated scanner; treat the offline DB as a fast
    first pass.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.