Works with the AI Agents you already use
Lockfile Diff + SBOM
Diff lockfiles and generate CycloneDX-lite SBOMs to identify major bumps, install scripts, and git dependency risks.
$19
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
| Metric | Count |
|---|---|
| Added Packages | 4 |
| Removed Packages | 2 |
| Changed Packages | 12 |
| Major Bumps | 2 |
| Git/URL Signals | 1 |
| Install Scripts | 1 |
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
- Run
npm auditto check the 4 new packages for known vulnerabilities. - Verify the
d3-colorgit hash to ensure it points to a tagged release. - Review the
zodv3 migration guide for breaking schema changes.
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
installscripts 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
- Selection of the mode (
difforsbom) and the target file paths or project directories. - Execution of the bundled Node.js script to parse lockfile structures without making any network calls.
- Analysis of the generated JSON report to prioritize new external sources, scripts, and major version shifts.
- 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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Permissions
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.