SBOM Generator & Vulnerability Scan

    1

    Generate CycloneDX SBOMs and scan Maven or npm dependencies for vulnerabilities and CVEs.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    SBOM Generator & Vulnerability Scan

    Example session with this skill installed

    Run a security scan on the current npm project and generate a CycloneDX SBOM.

    • Read your context and instructions
    • Compiled the sbom generator

    I have completed the security analysis for the project located at the current root.

    Data Disclosure Notice: I uploaded package-lock.json to https://www.depanalyzer.com/api/scan as requested to perform the vulnerability check.

    Security Scan Summary

    ItemDetails
    Detected Ecosystemnpm
    Project Root/workspaces/web-app
    SBOM StatusSuccess (security/bom.json)
    Component Count142 dependencies
    Scan StatusSuccess (security/depanalyzer-results.json)
    Vulnerability Count3 (1 High, 2 Medium)
    Git HygieneAdded security/ to .gitignore

    Scan Results Detail

    {
      "summary": {
        "total_vulnerabilities": 3,
        "severity_counts": {
          "CRITICAL": 0,
          "HIGH": 1,
          "MEDIUM": 2,
          "LOW": 0
        }
      },
      "vulnerabilities": [
        {
          "id": "CVE-2023-45853",
          "package": "body-parser",
          "version": "1.19.0",
          "severity": "HIGH",
          "description": "Buffer overflow in request handling"
        },
        {
          "id": "CVE-2024-21172",
          "package": "lodash",
          "version": "4.17.20",
          "severity": "MEDIUM",
          "description": "Prototype pollution in merge function"
        },
        {
          "id": "CVE-2023-22515",
          "package": "debug",
          "version": "4.3.1",
          "severity": "MEDIUM",
          "description": "Regular expression denial of service"
        }
      ]
    }
    

    Next steps

    1. Run sbom-fix-vulnerability to automatically patch the identified body-parser and lodash issues.
    2. Review security/bom.json to verify the full dependency tree.
    3. Delete the security/ folder after remediation if you do not wish to keep local copies of the scan logs.

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

    About this skill

    Manual dependency auditing is slow and prone to oversight. This skill automates Software Composition Analysis (SCA) by generating standard CycloneDX SBOMs and running vulnerability scans against a live database.

    What it does

    • Ecosystem detection automatically identifies Maven, npm, or Gradle projects and their respective root directories.
    • SBOM generation creates a standard CycloneDX JSON bill of materials for all declared dependencies.
    • Vulnerability scanning submits manifests to DepAnalyzer to identify active CVEs and security risks.
    • File management organizes results into a dedicated security directory while ensuring sensitive scan data is not committed to version control.
    • Validation checks for valid JSON structures and non-empty component arrays to ensure data integrity.

    How it works

    1. Point the tool at a project path to trigger ecosystem detection via pom.xml, package.json, or Gradle build files.
    2. Confirm data disclosure for the DepAnalyzer scan if using Maven or npm.
    3. Review the generated security/bom.json for a complete inventory of project components.
    4. Analyze the security/depanalyzer-results.json to identify specific vulnerabilities and their severity levels.

    Frameworks & tools

    The skill utilizes ecosystem-specific CycloneDX tools, the DepAnalyzer API, and standard manifest files including pom.xml, package-lock.json, and build.gradle.

    Why this beats prompting it yourself

    Writing reliable SBOMs requires specific CLI tool knowledge and precise command flags for every ecosystem. This skill handles the environment-specific logic, validates the output against the CycloneDX schema, and manages the network interaction with DepAnalyzer without manual payload formatting.

    Use cases

    • Generate a compliance-ready SBOM for a new release or customer request.
    • Audit a legacy repository for known CVEs before starting a refactor.
    • Prep security data as input for automated dependency patching workflows.
    • Verify that third-party library versions are correctly documented and tracked.

    Known limitations

    Gradle projects support SBOM generation but are not supported by the DepAnalyzer vulnerability scan. Network access is required for scanning Maven and npm dependencies.

    Gradle lacks DepAnalyzer scan support. Requires outbound HTTPS access to depanalyzer.com. Does not patch or modify code.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    • Free with an Agensi account

    Requires

    Depanalyzer
    @cyclonedx/cyclonedx-npm
    Node.js

    Permissions

    Network Access
    Read Files
    Write Files

    Allowed Hosts

    www.depanalyzer.com
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    The skill currently supports Maven and npm for full vulnerability scanning via DepAnalyzer. While it can generate CycloneDX SBOMs for Gradle projects, the automated vulnerability analysis feature is not yet available for the Gradle ecosystem.

    This skill automates the complex CLI commands and schema validation required to generate compliant CycloneDX files. Unlike a simple prompt, it handles ecosystem detection, ensures data integrity through JSON validation, and manages the API handshake for security scans.

    No manual installation of scanning tools is required; the skill is designed to interface directly with your project's manifest files. As long as your project contains a standard pom.xml, package.json, or build.gradle, the skill can initiate the audit.

    The skill generates a dedicated 'security' directory within your project to store the CycloneDX BOM and scan results. It is configured to keep these files local and organized, ensuring sensitive vulnerability data isn't accidentally pushed to public version control.

    The skill performs a structural validation of the generated JSON to ensure the bill of materials is not empty and conforms to standard schemas. This ensures that the data you receive is ready for compliance reporting or further automated processing.

    New in LLM Ops