Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Lockfile Diff + SBOM

    1

    Diff lockfiles and generate CycloneDX-lite SBOMs to identify major bumps, install scripts, and git dependency risks.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Lockfile Diff + SBOM

    Lockfile Diff + SBOM

    Example session with this skill installed

    Run a diff between the old-lock.json and the new package-lock.json in the current directory. Identify major bumps and any new git dependencies.

    • Read your context and instructions
    • Compiled the lockfile diff

    I have compared the two lockfiles using the bundled script. The analysis is complete.

    Dependency Review: old-lock.json -> package-lock.json

    MetricCount
    Added Packages4
    Removed Packages2
    Changed Packages12
    Major Bumps2
    Git/URL Signals1
    Install Scripts1

    Risk Analysis

    • git/url: d3-color@3.1.0 -> git+https://github.com/d3/d3-color.git#main (New source)
    • install scripts: esbuild@0.20.1 (carried by npm v3 lockfile)
    • major bumps: lucide-react (0.344.0 -> 1.0.0), zod (2.3.0 -> 3.22.0)

    Package Details

    • Added: clsx, tailwind-merge, is-mobile, debug
    • Removed: lodash.assign, request
    • Changed: react (18.2.0 -> 18.3.1), typescript (5.3.3 -> 5.4.2), vite (5.1.0 -> 5.2.0)

    Notes: The d3-color change to a git URL bypasses registry immutability. Verify if this was intentional. The lucide-react bump is a major version change; check for breaking API changes in their migration guide.

    Next steps

    1. Run npm audit to check the 4 new packages for known vulnerabilities.
    2. Verify the d3-color git hash to ensure it points to a tagged release.
    3. Review the zod v3 migration guide for breaking schema changes.
    old-lock.json

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

    About this skill

    Dependency changes are a primary vector for supply chain attacks and breaking releases. This skill identifies exactly what changed in your lockfiles, flagging high-risk signals like major version bumps, new install scripts, and dependencies pulled from unverified git or non-registry URLs. It provides a zero-dependency, offline mechanism to audit package changes before they hit production.

    What it does

    • Diff lockfiles across formats, including npm, Yarn, and pnpm, to compare package names and resolved versions.
    • Identify risk signals by flagging new install scripts and dependencies resolved from git repositories or direct URLs.
    • Detect major bumps to highlight breaking change risks that require manual changelog review.
    • Generate SBOMs in a CycloneDX-lite JSON format for compliance and release inventory requirements.
    • Inventory components by extracting name, version, purl, and integrity hashes from local lockfile data.

    How it works

    1. Selection of the mode (diff or sbom) and the target file paths or project directories.
    2. Execution of the bundled Node.js script to parse lockfile structures without making any network calls.
    3. Analysis of the generated JSON report to prioritize new external sources, scripts, and major version shifts.
    4. Triage of findings, manually verifying any flagged git sources or potential typosquats.

    Frameworks & tools

    This tool uses a bundled Node.js script (v18+) with zero external dependencies. It supports package-lock.json, npm-shrinkwrap.json, yarn.lock, and pnpm-lock.yaml.

    Why this beats prompting it yourself

    Parsing complex lockfile formats like Yarn's line-based schema or nested npm trees is prone to hallucination and regex errors in raw LLM prompts. This skill uses a specialized, offline script to extract ground-truth data, ensuring that every reported version and risk signal is actually present in the file.

    Use cases

    • PR reviews to verify that a "simple dependency update" didn't sneak in an unverified git source.
    • Release audits to generate a component manifest for compliance before shipping a new version.
    • Migration checks to ensure version parity when switching from Yarn to npm or vice versa.
    • CI gating to automatically flag major version bumps or new install scripts in automated pipelines.

    Known limitations

    Does not perform vulnerability (CVE) scanning. Yarn and pnpm lockfiles do not support install script detection. pnpm support is best-effort due to the lack of a bundled YAML parser.

    No CVE scanning. Yarn and pnpm don't support install script flags. pnpm is best-effort. Requires Node 18+. Offline only.

    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 21 days ago

    Requires

    Node.js 18+
    Git
    Node.js

    Permissions

    Terminal / Shell
    Read Files

    Reads lockfiles (package-lock, npm-shrinkwrap, yarn.lock, pnpm-lock.yaml) and prints JSON to stdout. Not a CVE scanner by design — pair with your audit tooling for vulnerability status.

    Listed1 month ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    This skill uses a specialized, offline Node.js script to extract exact version data and risk signals, preventing the hallucinations and regex errors that occur when asking a standard LLM to read complex lockfile schemas.

    The skill fully supports npm (package-lock.json, shrinkwrap), Yarn (yarn.lock), and pnpm (pnpm-lock.yaml), allowing you to audit changes or verify parity during package manager migrations.

    It flags high-risk indicators such as major version bumps that may contain breaking changes, new post-install scripts, and dependencies sourced from unverified git repositories or direct URLs rather than official registries.

    No, this skill operates entirely offline and makes zero network calls; it parses your local files to generate reports, ensuring your dependency data never leaves your secure environment.

    The skill identifies what is in your project and flags suspicious sources, but it does not query external vulnerability databases (like the NVD) to report on specific CVEs.

    You receive the core AI skill configuration along with the bundled, zero-dependency Node.js execution script required to perform the deep parsing and SBOM generation.

    New in Security