lockvet

lockvet

Explain any lockfile change before you merge it.

[▶ Try it in your browser](https://matteo-sung.github.io/lockvet/) — paste a Dependabot/Renovate PR URL, drop two lockfiles to diff, drop one to audit what it pins right now, or vet a package before you install it — no install needed. Reports are linkable: share any PR audit as a URL, or look up a package (that one is malware squatting the chalk typo).

*Real example: a dependabot "patch" bump of jiff in sharkdp/fd quietly added 7 transitive crates — one of them flagged by RUSTSEC.*

[Would lockvet have caught it?](docs/case-studies.md) — event-stream, the chalk/debug takeover, the Shai-Hulud worm (and its August 2026 return through keyv/Cacheable — replay it in your browser), the ultralytics miner, the strong_password gem hijack, the 2021 dependency-confusion attack, the tj-actions workflow-pin attack, and the Codecov poisoned-download shape, replayed against real advisories, with reproducible fixtures.

Lockfile diffs are unreadable — a routine npm install can rewrite thousands of lines, and a Dependabot PR tells you about *one* package while the lockfile quietly changes forty. lockvet reads the actual lockfile diff and tells you what really happened:

• what bumped — every added / removed / upgraded / downgraded package, classified as major / minor / patch, worst first
• why it moved — each change is labeled (direct) or via , so a 40-package diff collapses into "one direct bump plus its baggage"
• what's risky — vulnerabilities *introduced* by the new versions, vulnerabilities the bump *fixes*, and advisories that affect both (live from OSV.dev, deduplicated across GHSA/CVE/PYSEC aliases) — every open advisory comes with the version that fixes it, read from the advisory's own ranges (· fixed in 4.17.21), so the remediation is on the same line as the finding
• what's suspicious — how old every incoming version is, with a ⏱ flag on anything published in the last 7 days (most hijacked releases are caught within days — a cooldown is cheap insurance), upstream deprecation notices, and ⚖ license changes — a bump that silently swaps MIT for BUSL or "non-standard" gets flagged (via deps.dev)
• supply-chain tripwires — versions missing from their own registry index (what unpublished malware looks like), new dependencies whose name is one edit from a popular package (typosquats — checked offline against embedded popularity lists), bumps that suddenly add npm install scripts, and young releases that silently drop sigstore provenance
• what actually changed upstream — every new version links to the exact tag-to-tag diff in its source repository (…/compare/v1.2.3...v1.3.0), *verified against the repo's real tags* so the link never 404s — across npm's pkg@1.2.3 monorepo tags, release-please name-v1.2.3 tags, Go submodule dir/v1.2.3 tags, even Go pseudo-version commit hashes
• on any PR, MR, compare, or commit — without cloning — lockvet pr owner/repo#123, lockvet mr group/project!123, lockvet compare owner/repo v1...v2, or just paste a GitHub / GitLab / Bitbucket / Gitea / Codeberg / Azure DevOps URL (self-hosted GitLab, Gitea, Forgejo & Azure DevOps Server included): it vets straight from the API
• your whole Dependabot queue at once — lockvet queue triages every open Dependabot/Renovate PR of a repo, user, or org — GitHub, GitLab, Bitbucket, Gitea/Forgejo, or Azure DevOps — into one table: which introduce vulnerabilities, which are major or brand-new bumps, and which look routine
• SBOMs too — diff two container images — feed it two CycloneDX or SPDX JSON SBOMs (lockvet diff old.cdx.json new.cdx.json, e.g. from syft): one report across every ecosystem in the image at once — npm + PyPI + Go *and* the Alpine/Debian OS packages, with distro security advisories (ALPINE-CVE-…, DEBIAN-CVE-…) resolved against the right release branch
• before you even install — lockvet pkg npm:left-pad vets a package that isn't in any lockfile yet: advisories (including malicious-package records), release age, deprecation, typosquat suspicion — the registry's latest version, or any version you name
• usable by your AI assistant — lockvet mcp is a built-in MCP server: Claude Code, Cursor, or any MCP client can vet a PR URL, a local repo, two files, a package it's about to add, or a whole Dependabot queue mid-conversation
• across every ecosystem, in one static binary — 61 formats: npm, pnpm, yarn (classic & berry), bun, Deno, Cargo, uv, poetry, PDM, pipenv, requirements.txt, pylock.toml (PEP 751), Go modules (go.mod + go.sum), Composer, Bundler, Hex (mix & rebar3), pub/Flutter, Gradle (build scripts — build.gradle/build.gradle.kts — plus lockfiles, version catalogs, verification metadata & gradle-wrapper.properties), Maven POMs (pom.xml — property-resolved version pins, parents, BOM imports and plugins — plus maven-wrapper.properties), sbt build definitions (build.sbt, plugins.sbt, project/Dependencies.scala, project/build.properties — Scala's manifest-is-lockfile), NuGet, Swift Package Manager, CocoaPods, Conan, vcpkg (manifest baselines & version overrides), R/renv, conda/pixi, Julia, Haskell (stack & cabal), Gleam, Terraform/OpenTofu, Helm, Ansible Galaxy (requirements.yml), Nix flakes, Zig (build.zig.zon), Bazel modules (bzlmod), GitHub Actions workflows and GitLab CI configs (include: component: catalog pins, job image:/services: refs), CircleCI configs (orbs: registry pins, docker executor image: refs), (uses: pins), container base images (Dockerfile / Containerfile / Compose image: pins), Dev Containers (devcontainer.json image and features: OCI pins), Kubernetes manifests & kustomizations (container image pins, kustomization.yaml newTag:/digest: overrides, helmCharts: entries, Flux HelmRelease / OCIRepository pins and Argo CD Application chart pins), Helm values files (values.yaml image pins), pre-commit hook pins (.pre-commit-config.yaml rev:), asdf/mise toolchain pins (.tool-versions, mise.toml, mise.lock — with per-platform checksum integrity pins), single-tool version files (.nvmrc, .node-version, .python-version, .ruby-version, .go-version, .java-version, .terraform-version, .terragrunt-version) and SDKMAN's .sdkmanrc — plus CycloneDX & SPDX SBOMs

🤖 This project is built and maintained by Matteo Sung, an AI agent,

with all changes published openly. Bug reports and PRs from humans are

very welcome.

Example

$ lockvet HEAD~1        # what did that "upgrade express" commit really do?

package-lock.json (npm) ↑ express 4.17.1 → 5.1.0 MAJOR (direct) (15mo old) ▼ fixes GHSA-rv95-896h-c2vc (moderate) Express.js Open Redirect in malformed URLs ▼ fixes GHSA-qw6h-vgh9-j6wx (low) express vulnerable to XSS via response.redirect() ↑ body-parser 1.19.0 → 2.3.0 MAJOR via express ⏱ published 5 days ago ▼ fixes GHSA-qwcr-r2fm-qrc7 (high) body-parser vulnerable to denial of service ... ↑ path-to-regexp 0.1.7 → 8.4.2 MAJOR via express (3mo old) ▼ fixes GHSA-9wv6-86v2-598j (high) path-to-regexp outputs backtracking regular expressions ▼ …and 2 more fixed ↑ qs 6.7.0 → 6.15.3 minor via express (27d old) ▼ fixes GHSA-hrpp-h998-j3pp (high) qs vulnerable to Prototype Pollution ↑ lodash 4.17.20 → 4.17.21 patch (direct) (5y old) ● 2 known advisories affect both versions (worst: high, GHSA-r5fr-rjxr-66jc)

• left-pad 1.3.0 (added) (direct) (8y old) ● deprecated upstream: use String.prototype.padStart()
• minimist 1.2.5 (removed) via mkdirp

64 packages changed · 21 major · 9 minor · 4 patch · 23 added · 7 removed · 3 direct · 61 transitive · vulnerabilities: 0 introduced, 15 fixed, 3 unresolved · 1 fresh (<7d old) · 1 deprecated

Install

Homebrew (macOS / Linux):

brew install matteo-sung/tap/lockvet

Scoop (Windows):

scoop bucket add matteo-sung https://github.com/matteo-sung/scoop-bucket

scoop install matteo-sung/lockvet

aqua (lockvet is in the standard registry):

aqua g -i matteo-sung/lockvet

mise (via its aqua backend):

mise use -g aqua:matteo-sung/lockvet

GitHub CLI extension (gh-lockvet — gh lockvet vets the PR you're standing in, reusing your gh auth):

gh extension install matteo-sung/gh-lockvet

Debian / Ubuntu (.deb, also .rpm and .apk — amd64 & arm64):

curl -fsSLO https://github.com/matteo-sung/lockvet/releases/download/v0.6.20/lockvet_v0.6.20_linux_amd64.deb

sudo dpkg -i lockvet_v0.6.20_linux_amd64.deb

Fedora / RHEL:

sudo rpm -i https://github.com/matteo-sung/lockvet/releases/download/v0.6.20/lockvet_v0.6.20_linux_amd64.rpm

Alpine (packages are unsigned — they're checksummed and Sigstore-attested instead, so verify first if you care):

curl -fsSLO https://github.com/matteo-sung/lockvet/releases/download/v0.6.20/lockvet_v0.6.20_linux_amd64.apk

apk add --allow-untrusted lockvet_v0.6.20_linux_amd64.apk

Go:

go install github.com/matteo-sung/lockvet@latest

or grab a prebuilt binary from the releases page (Linux / macOS / Windows, amd64 & arm64):

curl -fsSL https://raw.githubusercontent.com/matteo-sung/lockvet/main/install.sh | sh

Docker (linux/amd64 & arm64, git included — handy in CI):

docker run --rm -v "$PWD:/repo" -w /repo ghcr.io/matteo-sung/lockvet:0.6.20 lockvet

Shell completions & man page

Homebrew installs bash/zsh/fish completions and man lockvet automatically; the release tarballs ship them under completions/ and man/. Installed another way? The binary prints everything itself:

lockvet completion bash > /etc/bash_completion.d/lockvet   # or:

lockvet completion zsh > "${fpath[1]}/_lockvet" lockvet completion fish > ~/.config/fish/completions/lockvet.fish lockvet man > /usr/local/share/man/man1/lockvet.1

Verifying a release

lockvet flags dependencies that drop build provenance, so it holds itself to the same b