Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dependency Vulnerability Scanner

    1

    Scan project lockfiles for known vulnerabilities using the OSV.dev database and generate SBOM reports.

    $1.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dependency Vulnerability Scanner

    Dependency Vulnerability Scanner

    Example session with this skill installed

    Audit the package-lock.json in my current directory for vulnerabilities and output a summary table.

    • Read your context and instructions
    • Compiled the dependency vulnerability scanner

    I have scanned package-lock.json against the OSV.dev database. I identified 4 vulnerabilities across 2 packages, including one high-severity issue with a direct fix available.

    Dependency Vulnerability Audit

    PackageVersionSeverityIDFixed InType
    axios0.21.1HighCVE-2021-37490.21.2Direct
    nth-check2.0.0ModerateCVE-2021-38032.0.1Transitive
    loader-utils1.4.0ModerateCVE-2022-376011.4.2Transitive
    loader-utils1.4.0LowCVE-2022-376032.0.3Transitive

    Summary of Findings:

    • Critical/High: 1 issue detected. Immediate action recommended for axios.
    • Transitive: 3 issues detected in nested dependencies.
    • Remediation: All identified vulnerabilities have higher versions available that resolve the security flaws.

    Next steps

    1. Run npm install axios@0.21.2 to resolve the high-severity SSRF vulnerability.
    2. Execute npm audit fix to attempt automatic resolution of the transitive loader-utils and nth-check issues.
    3. Integrate dep_scan.py --fail-on high into your CI pipeline to prevent new vulnerable packages from being merged.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Supply chain attacks often hide in plain sight within your deep dependency tree. This skill automates software composition analysis (SCA) to identify known vulnerabilities across multiple ecosystems before they reach production.

    What it does

    • Multi-manifest parsing identifies dependencies in Python, JavaScript, Go, Rust, Ruby, PHP, Java, and .NET lockfiles.
    • Vulnerability matching queries the OSV.dev database to find active CVEs and GHSAs affecting your specific versions.
    • SBOM generation produces a complete inventory of project packages in JSON or CSV formats.
    • CI enforcement provides exit codes to block builds containing high-severity vulnerabilities.
    • Remediation guidance highlights fixed versions and distinguishes between direct and transitive risks.

    How it works

    1. Targeting involves pointing the scanner at a project root or specific manifest files like package-lock.json or poetry.lock.
    2. Analysis parses the local files to build a dependency graph and identify pinned versions.
    3. Lookup sends batches of package identifiers to the OSV API for real-time vulnerability status.
    4. Reporting outputs a prioritized list of risks or a full inventory based on the selected flags.

    Frameworks & tools

    This tool uses Python to interface with the OSV.dev API. It supports npm, yarn, pnpm, pip, poetry, pipenv, cargo, composer, maven, and nuget lockfile formats.

    Why this beats prompting it yourself

    Manual audits miss nested transitive dependencies and quickly become outdated as new CVEs are published. This skill performs precise version-matching against the OSV database, providing machine-readable outputs that a standard LLM cannot generate through reasoning alone.

    Use cases

    • Audit a legacy repository for high-severity vulnerabilities and technical debt.
    • Verify if a specific reported CVE affects any packages in your current stack.
    • Generate a CSV-based SBOM for compliance or security documentation.
    • Add an automated security gate to a GitHub Actions or GitLab CI pipeline.

    Known limitations

    Unpinned requirements, such as those using version ranges in a requirements.txt file, cannot be checked for precise vulnerabilities. Analysis of reachability for specific functions is not automated.

    Cannot precisely check unpinned requirements or version ranges. Does not perform automated reachability analysis of vulnerable code paths.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Osv
    Python

    Permissions

    Terminal / Shell
    Read Files

    Allowed Hosts

    api.osv.dev
    Listed1 month ago
    Updated28 days ago

    What's inside

    Frequently Asked Questions

    The scanner identifies vulnerabilities across a wide range of ecosystems, including Python (pip, poetry), JavaScript (npm, yarn, pnpm), Go, Rust, Ruby, PHP, Java, and .NET. It works by parsing specific lockfiles to ensure precise version matching against the OSV database.

    This skill is designed to integrate with any AI agent capable of executing Python-based tools and accessing local or repository files. It provides machine-readable outputs (JSON/CSV) that allow the agent to summarize risks or automate PR comments for security fixes.

    Unlike general prompts, this skill uses precise version-matching logic to query the live OSV.dev database, catching deep transitive dependencies that LLMs often hallucinate or overlook. It also generates valid SBOM files, which is a structural task LLMs cannot reliably perform through reasoning alone.

    No, the scanner does not require access to your source code; it only needs to read your dependency manifest files (like package-lock.json). The package identifiers are then checked against the public OSV API without exposing your proprietary logic.

    Yes, the skill includes a CI enforcement mode that returns specific exit codes based on vulnerability severity. You can configure it to automatically fail builds or pull requests if high-severity CVEs are detected in your dependency tree.

    New in Security