PAGES
← all tools
◆ SAST / SCA / Code Security

cve-lite-cli

v1.40.0 open-source

CVE Lite CLI is a command-line tool that scans project lockfiles for vulnerabilities and provides copy-and-run fix commands.

Summary

cve-lite-cli is an open-source command-line tool that scans JavaScript and TypeScript lockfiles for known CVEs and returns copy-and-run fix commands rather than just a list of findings. It runs locally on a developer's machine or in CI, with nothing leaving the environment during a scan, and outputs to terminal, JSON, HTML, or SARIFSARIFStatic Analysis Results Interchange Format, a standard for sharing code-analysis findings, including locations and rule details. It lets scanners report results to a common review interface. for GitHub Code Scanning ingestion. It's aimed at application developers and appsec teams who need remediation guidance, not just detection, including flags for maintenance-risk constraint drag, override hygiene, and offline advisory databases for air-gapped work. It carries OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Lab Project recognition, distinguishing it from generic scanners in the space rather than positioning against a named competitor. Release activity is frequent and recent, spanning new detection rules, SARIF fingerprinting, and multi-folder scan support, indicating active maintenance.

CVE Lite CLI is a command-line tool that scans project lockfiles for vulnerabilities and provides copy-and-run fix commands.

How cve-lite-cli helps

Which known CVEs are sitting in this project's lockfile right now?

scans the lockfile locally against OSV and npm registry advisory data and lists each finding with severity, no code or dependency tree leaving the machine

How do I actually fix the vulnerabilities this scan just found?

pairs each finding with a copy-and-run fix command, auto-applying safe within-range transitive refreshes when the fix is available inside the parent's declared range

Which direct dependencies are the real blockers behind a transitive vulnerability I can't clear?

the maintenance-risk rule flags direct dependencies whose major-version constraint is holding back a transitive fix, or that are deprecated on npm, and shows the top-level Root package behind each transitive finding

Are my dependency overrides doing anything useful, or just dead weight and hidden risk?

audits override hygiene for phantom imports sourced only through an override or transitive pin, and flags override floors already satisfied by every parent declaration as redundant

Can I scan and get fix guidance on a machine with no network access?

an offline advisory database can be bootstrapped ahead of time so scans run against local data with no runtime API calls

all 25 features, with the evidence for each →

Languages

Not documented

Features

25 capabilities across 6 capability groups · 2 backed by code, an API document or a real run

Built from cve-lite-cli's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • cve-lite-cli covers 4 of the 5 supply chain security capabilities we track.
  • cve-lite-cli covers 2 of the 8 vulnerability assessment methods capabilities we track.

What cve-lite-cli offers you

  • Command-line interface9
  • CI/CD pipeline integration7
  • JSON data export5
  • Air-gapped deployment1
  • Offline mode1
  • Scheduled jobs1
CycloneDX SBOM 1 feature Supply chain security since 2026
CycloneDX SBOM output shipped Exports software bills of materials in CycloneDX format, supporting spec version 1.6 with tools.components object form. 5 releases · 1 other source · first seen May 2026

Shared capability: CycloneDX SBOM

Also counts toward: Command-line interface

release

  • The specVersion field in CycloneDX output is now 1.6 (up from 1.4), changing the schema version for downstream tools diffing or asserting on SBOM metadata. v1.34.0 · Sep 2026 · source · release history
  • Adds --sbom cyclonedx as an alias path to CycloneDX output (alongside the existing --cdx), now emitting spec version 1.6 with tools.components object form using publisher. v1.34.0 · Sep 2026 · source · release history
  • metadata.tools in CycloneDX output now uses the 1.6 tools.components object form with publisher, replacing the deprecated 1.4 array of {vendor, name, version}; downstream consumers parsing metadata.tools will see a different structure. v1.34.0 · Sep 2026 · source · release history
  • CycloneDX output (--cdx and --sbom cyclonedx) now emits specVersion 1.6 instead of 1.4; any CI pipeline or tooling that diffs SBOMs or asserts on the specVersion field will need updating. v1.34.0 · Sep 2026 · source · release history
  • Adds cdx input (default false) to the GitHub Action for enabling CycloneDX output v1.16.0 · May 2026 · source · release history

example

  • Enable CycloneDX output in a GitHub Actions workflow. - uses: cve-lite-cli/action@v1 with: cdx: true v1.16.0 · May 2026 · source
SPDX SBOM 1 feature Supply chain security since 2026
SPDX SBOM output shipped Exports software bills of materials in SPDX 2.3 format with vulnerability overlays attached as SECURITY external references. 1 release · 2 other sources · first seen Sep 2026

Shared capability: SPDX SBOM

Also counts toward: Command-line interface

release

  • Adds SPDX 2.3 SBOM output via --sbom spdx2.3 (also --sbom spdx); findings attach as SECURITY external references of type advisory, with severity and fix command in a package annotation; package licenses sourced from the npm lockfile at no network cost; pnpm, Yarn and Bun resolve to NOASSERTION; emits… v1.34.0 · Sep 2026 · source · release history

example

  • Generate a full SPDX 2.3 SBOM with vulnerability overlays attached as SECURITY references — useful for NTIA-compliant software bills of materials in regulated environments. cve-lite /path/to/project --sbom spdx2.3 v1.34.0 · Sep 2026 · source
  • Generate SPDX 2.3 SBOM output cve-lite /path/to/project --sbom spdx
Dependency scanning 1 feature Supply chain security since 2026
License compliance scanning shipped Scans dependencies for license compliance issues, generates compliance-ready SBOMs, and enforces non-zero exit codes on incomplete or non-compliant license data. 3 other sources · first seen May 2026

Shared capability: Dependency scanning

example

  • Run a scan that also reports license compliance issues in the output reports. cve-lite-cli --check-licenses v1.32.0 · Sep 2026 · source
  • Force a non-zero exit (code 3) if license or dependency data is incomplete. cve-lite-cli --incomplete-policy error v1.32.0 · Sep 2026 · source
  • Generate a compliance-ready SBOM of all dependencies in the current directory. cve-lite-scan --cdx v1.16.0 · May 2026 · source
Artifact signing 1 feature Supply chain security since 2026
Package verification and supply chain security shipped Cryptographically verifies downloaded release tarballs and npm packages using Sigstore-backed artifact attestations and npm signature checks. 1 release · 2 other sources · first seen May 2026

Shared capability: Artifact signing

release

  • Release tarballs are now cryptographically signed using GitHub's Sigstore-backed Artifact Attestations with ephemeral OIDC-issued keys. v1.12.1 · May 2026 · source · release history

example

  • Verify the signature of an npm-installed copy of cve-lite-cli. npm audit signatures v1.12.1 · May 2026 · source
  • Verify the cryptographic signature of a downloaded cve-lite-cli release tarball. gh attestation verify cve-lite-cli-X.Y.Z.tgz --repo OWASP/cve-lite-cli v1.12.1 · May 2026 · source
Vulnerability database matching 1 feature Vulnerability assessment methods since 2026
Offline advisory database shipped Sets up a local advisory database so the cyber tool can run scans in air-gapped environments without making any external API calls. 15 releases · 8 other sources · first seen Mar 2026

Shared capability: Vulnerability database matching

Also counts toward: Air-gapped deployment, Command-line interface, Offline mode

release 15 total

  • Usage scan's 5000-file cap is now disclosed in terminal, JSON, and HTML reporters rather than silent filtering. v1.38.0 · Oct 2026 · source · release history
  • New advisories init subcommand creates an empty offline advisory database for air-gapped environments to populate manually. v1.28.0 · Jul 2026 · source · release history
  • advisories init subcommand to create an empty offline advisory database for air-gapped environments v1.28.0 · Jul 2026 · source · release history
  • Adds --ca-cert <path> CLI flag to pass a PEM CA certificate for a single scan or advisory sync invocation v1.18.1 · May 2026 · source · release history
  • cve-lite config set ca-cert <path> saves a PEM CA certificate path persistently in ~/.cve-lite-cli/config.json for corporate SSL proxy support v1.18.1 · May 2026 · source · release history
  • --no-cache flag forces a fresh OSV query for all packages in a single scan, bypassing the queryEntries cache while still writing results back so subsequent runs benefit from caching as normal. Mutually exclusive with --offline and --offline-db. v1.14.0 · May 2026 · source · release history

example 8 total

  • Write all structured output to a dedicated reports directory so a CI step can hand a stable path to the next stage without globbing or renaming. cve-lite /path/to/project --sarif --json --output reports v1.37.0 · Sep 2026 · source
  • Initialize a local offline advisory database for use in air-gapped CI environments. cve-lite-cli advisories init v1.28.0 · Jul 2026 · source
  • Bootstrap an empty offline advisory database on an air-gapped machine, then scan without any runtime API calls. cve-lite advisories init && cve-lite /path/to/project --offline v1.28.0 · Jul 2026 · source
  • Scan or sync advisories through a corporate MITM proxy that requires a custom CA certificate. cve-lite scan --ca-cert /path/to/corporate-ca.pem v1.18.1 · May 2026 · source
  • Sync the DB to a custom file and scan using that specific local database. cve-lite advisories sync --output /path/to/advisories.db cve-lite /path/to/project --offline-db /path/to/advisories.db v1.1.0 · Apr 2026 · source
  • Sync advisories to a custom location and scan offline with that specific DB file. cve-lite advisories sync --output /path/to/advisories.db cve-lite /path/to/project --offline-db /path/to/advisories.db v1.1.1 · Apr 2026 · source
Vulnerability prioritization 1 feature Vulnerability assessment methods since 2026
Contextual prioritization signals shipped Attaches reachability, exposure, and usage signals to each verbose finding to help users prioritize which vulnerabilities warrant attention based on path depth, request-handling exposure, and dependency usage. 6 releases · first seen Apr 2026

Shared capability: Vulnerability prioritization

Also counts toward: Command-line interface

release

  • Adds reachability, exposure, and usage contextual prioritization signals to each verbose finding, surfaced separately from the EPSS prioritySignal; reachability reports path_depth_2 and above or falls back to direct_dependency, exposure flags findings whose path runs through a request-handling package,… v1.38.0 · Oct 2026 · source · release history
  • Usage scan's 5000-file cap is now disclosed in terminal, JSON, and HTML reporters rather than silent filtering. v1.38.0 · Oct 2026 · source · release history
  • Adds a Root column showing the top-level direct dependency behind each transitive finding, across terminal, JSON, and HTML report outputs (including multi-folder scans). v1.30.0 · Aug 2026 · source · release history
  • Root column showing the top-level direct dependency behind each transitive finding, across terminal, JSON, and HTML report (including multi-folder) v1.30.0 · Aug 2026 · source · release history
  • --usage and --only-used flags added to the CLI to enable static source code analysis for import reachability of vulnerable dependencies. v1.8.0 · Apr 2026 · source · release history
  • CLI tables now include a dedicated Usage column that displays import counts or marks entries as unused, color-coded red and green. v1.8.0 · Apr 2026 · source · release history
Other / not yet classified 19 features Features we have not matched to a capability yet. A suggested match is marked.
Override hygiene auditing verified Checks dependency overrides against a dedicated rule set for hygiene problems and can automatically correct issues it finds. 20 releases · 10 other sources · first seen Mar 2026

Also counts toward: Command-line interface

release 20 total

  • Introduces override-hygiene rule OA011 for floors exceeding every declaring package's range. v1.38.0 · Oct 2026 · source · release history
  • If you gate CI on --check-overrides, re-run it after upgrading: OA010 was previously unreachable from the scan path and no-oped silently, so a prior clean result may not have been a genuine pass. v1.38.0 · Oct 2026 · source · release history
  • Adds new override-hygiene rule OA011 — detects an override floor that exceeds every declaring package's range — joining the OverrideRuleId union alongside OA001–OA010. v1.38.0 · Oct 2026 · source · release history
  • Changes lockfile selection logic to prefer the file named by packageManager in package.json when present, improving accuracy for projects with multiple lockfiles v1.36.0 · Sep 2026 · source · release history
  • Adds OA010 override-hygiene rule to flag an override floor that admits a known-vulnerable version v1.35.0 · Sep 2026 · source · release history
  • Adds override-hygiene rule OA010: flags an override floor that itself admits a known-vulnerable version, surfacing floors that appear protective but are not.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.35.0 · Sep 2026 · source · release history

docs

  • OA010.md OA010.md Reference docs for the ten override-hygiene rules ( OA010 OA009: Stale override floor OA010: Floor admits a vulnerable version tracks worst admitted advisory OA010.md enable OA007 registry drift + OA010 admitted-range checks (opt-in network) seen Sep 2026 · source

command line

  • --check-overrides — adds override auditing to a regular scan. For a dedicated override-only run, use the `overrides` subcommand: v1.27.0 · Jul 2026 · command-line history

example 8 total

  • Run the new OA011 rule to find override floors that exceed all declaring package ranges. cve-lite . --check-overrides v1.38.0 · Oct 2026 · source
  • Run an override hygiene audit to catch floors that admit vulnerable versions (OA010) alongside other override problems, without running a full CVE scan. cve-lite /path/to/project overrides v1.35.0 · Sep 2026 · source
  • Include override hygiene (including the new OA010 rule) in a single pass with the regular CVE scan, so vulnerable-floor overrides surface alongside CVE findings. cve-lite /path/to/project --check-overrides v1.35.0 · Sep 2026 · source
  • Auto-fix transitive vulnerabilities in-range without upgrading parents — useful in CI to land the smallest safe change. cve-lite /path/to/project --fix v1.30.0 · Aug 2026 · source
  • Run override hygiene auditing with auto-fix on a non-root project path using the new path-first argument order. cve-lite ./packages/api overrides --fix v1.27.0 · Jul 2026 · source
  • Automatically repair invalid overrides in-place using safe RFC 6902 patches. cve-lite overrides ./package.json --fix v1.25.0 · Jun 2026 · source
HTML report shipped Produces an HTML report covering scan findings, skipped dependencies, completeness gaps, and a light/dark mode toggle that persists across sessions. 23 releases · first seen Apr 2026

release 23 total

  • The --all findings table drops the IDs column; advisory IDs remain available in --verbose, JSON, SARIF, CycloneDX, and the HTML report. v1.38.0 · Oct 2026 · source · release history
  • The usage scan's 5000-file cap is now disclosed in the terminal, in --json, and in both HTML reporters, scoped per folder in multi-folder mode; a truncated scan records unknown for the contextual usage signal rather than claiming a package is unused. v1.38.0 · Oct 2026 · source · release history
  • Improves remediation command accuracy by caching full advisory records instead of IDs, preventing broken upgrade recommendations on repeated scans v1.36.0 · Sep 2026 · source · release history
  • Shows every known dependency path for a finding in the HTML report, capped at five paths per panel v1.35.0 · Sep 2026 · source · release history
  • Shows every known dependency path for a finding in the HTML report (capped at five paths per panel), replacing the previous single-primary-path display. v1.35.0 · Sep 2026 · source · release history
  • Adds a prod-vs-dev split line in compact and verbose terminal output and as a note in the HTML report severity card strip, showing 'N of M findings in prod dependencies' when some findings are dev-only. v1.34.0 · Sep 2026 · source · release history
Maintenance-risk detection shipped Identifies direct dependencies that are deprecated, abandoned, or holding back a transitive CVE fix through a major-version constraint, with graduated severity levels. 11 releases · 8 other sources · first seen Mar 2026

Also counts toward: CI/CD pipeline integration, Command-line interface, JSON data export

release 11 total

  • --check-maintenance now reports deprecated npm packages as distinct medium severity findings (graduated from drag high to deprecation medium) with a Last release context line for packages abandoned 2+ years v1.29.0 · Aug 2026 · source · release history
  • Expands DM001 maintenance-risk detection (--check-maintenance): deprecated npm packages now produce their own medium-severity finding (separate from constraint-drag findings); severity is graduated — constraint drag is high, deprecation is medium; packages abandoned 2+ years show a Last release context line. v1.29.0 · Aug 2026 · source · release history
  • --check-maintenance flag enabling DM001 detection of maintenance risks in direct dependencies v1.28.0 · Jul 2026 · source · release history
  • New --check-maintenance flag (rule DM001) flags direct dependencies that block a transitive CVE fix via major-version constraint drag, or that are deprecated on npm; renders in terminal, JSON, multi-folder, and HTML report, and counts toward --fail-on (high severity for constraint drag, medium for deprecated… v1.28.0 · Jul 2026 · source · release history
  • Adds --create-pr flag to cve-lite-cli that commits lockfile changes and opens a GitHub PR via gh after running with --fix v1.20.0 · Jun 2026 · source · release history
  • Workspace-scoped direct fix commands now include the appropriate workspace flag (npm install -w <workspace>, pnpm add --filter ./path, yarn workspace <name> add, bun add --filter <name>) for npm, pnpm, yarn, or bun workspace projects v1.18.1 · May 2026 · source · release history

docs

  • --create-pr After --fix, commit changes and open a GitHub pull request (requires gh cve-lite --fix --create-pr --base <branch> main Base branch for --create-pr cve-lite --fix --create-pr --base develop --debug Write verbose runtime/network diagnostics to a timestamped log file cve-lite --debug Use the local advisory… docs update · Aug 2026 · source
  • --create-pr After --fix, commit changes and open a GitHub pull request (requires gh cve-lite --fix --create-pr --base <branch> main Base branch for --create-pr cve-lite --fix --create-pr --base develop --debug Write verbose runtime/network diagnostics to a timestamped log file cve-lite --debug docs update · Aug 2026 · source

example

  • Fail CI on any high-severity constraint-drag finding (DM001) while also auditing override hygiene across all workspace packages. cve-lite /path/to/monorepo --check-maintenance --check-overrides --fail-on high v1.29.0 · Aug 2026 · source
  • Scan for maintenance risks (DM001) where direct dependencies block transitive CVE fixes. cve-lite-cli scan --check-maintenance v1.28.0 · Jul 2026 · source
  • Catch direct dependencies that are blocking a transitive CVE fix or are npm-deprecated, and fail CI on any high-severity finding. cve-lite /path/to/project --check-maintenance --fail-on high v1.28.0 · Jul 2026 · source
  • Automate vulnerability remediation by fixing lockfile and opening a PR with summary details. cve-lite-cli --fix --create-pr --base develop v1.20.0 · Jun 2026 · source
  • Apply automated, conservative fixes to direct dependencies in a project and verify the results. cve-lite-cli --fix v1.5.2 · Apr 2026 · source
  • Enforce a high-severity policy in CI pipelines by failing the build if high CVEs are detected with verbose context. cve-lite . --verbose --fail-on high v1.0.4 · Mar 2026 · source
SARIF output shipped suggested Exports findings as a SARIF file structured for full compatibility with GitHub Code Scanning, including cooldown warnings in the result properties. 10 releases · 4 other sources · first seen Apr 2026

Suggested capability: Static application security testing. This is our guess, not confirmed.

Also counts toward: CI/CD pipeline integration, JSON data export

release 10 total

  • SARIF rule help markdown now leads with a link to the project so a triaging analyst can identify which tool produced each Code Scanning alert. v1.40.0 · Oct 2026 · source · release history
  • Adds --output flag to set the directory for --json, --sarif, and --sbom outputs v1.37.0 · Sep 2026 · source · release history
  • Surfaces release-cooldown warnings in SARIF output as properties.cooldownWarning on the result, making them visible in GitHub Code Scanning. v1.29.0 · Aug 2026 · source · release history
  • SARIF output surfaces release-cooldown warnings via the properties.cooldownWarning field on result objects for GitHub Code Scanning v1.29.0 · Aug 2026 · source · release history
  • Adds --sarif output with ruleIndex, kind: "open", and partialFingerprints fields for full GitHub Code Scanning compatibility; shared fingerprint logic extracted to src/utils/sarif.ts. v1.27.0 · Jul 2026 · source · release history
  • --sarif can now be combined with --report to write both a SARIF file and an HTML report in one scan v1.24.0 · Jun 2026 · source · release history

example

  • Catch overrides pinned above every parent's declared range (OA011) alongside the full CVE scan, and emit SARIF for GitHub Code Scanning. cve-lite /path/to/project --check-overrides --sarif v1.38.0 · Oct 2026 · source
  • Generate a SARIF report with full GitHub Code Scanning fingerprinting to upload as a code-scanning artifact in CI. cve-lite /path/to/project --sarif v1.27.0 · Jul 2026 · source
  • Access the new SARIF utility for custom fingerprinting logic within a script. import { sarifFingerprintHash } from './src/utils/sarif.js'; v1.27.0 · Jul 2026 · source
  • SARIF output for GitHub Code Scanning cve-lite /path/to/project --sarif
Dependency fix application shipped Applies suggested dependency upgrades, generates executable fix commands based on lockfile type, maps hoisted parent chains, and reports fix coverage counts. 9 releases · 3 other sources · first seen Apr 2026

Also counts toward: Command-line interface

release 9 total

  • The recommended upgrade version for a transitive finding now resolves the parent from the finding's own dependency path, so some previously reported fix versions will change. v1.40.0 · Oct 2026 · source · release history
  • Adds fix coverage count ("Running these commands should fix X of Y findings") to terminal and HTML output for lockfile-refresh targets v1.18.0 · May 2026 · source · release history
  • Adds pnpm update, yarn upgrade, and bun update commands to --fix when the parent's declared range already covers the fixed transitive dependency version v1.18.0 · May 2026 · source · release history
  • Adds runnableFixCommand: string | null field to serialized findings for programmatic consumers. v1.12.0 · May 2026 · source · release history
  • Builds a logical dependency graph from package-lock.json to map hoisted packages back to their actual parent chain v1.11.0 · Apr 2026 · source · release history
  • Recommends npm update <parent> for npm transitive findings when a safe child version is reachable within the current parent dependency range v1.11.0 · Apr 2026 · source · release history

example

  • Install dev dependencies as a side effect of the fix command. cve-lite fix -D v1.24.0 · Jun 2026 · source
  • View fix suggestions with clear breaking change indicators before upgrading major versions. cve-lite-cli fix bun.lock v1.6.0 · Apr 2026 · source
  • Apply a suggested fix for a Node.js dependency based on the lockfile type npm install jsonwebtoken@4.2.2 express-jwt@2.1.0 sanitize-html@2.17.2 v1.3.0 · Apr 2026 · source
Report output format control verified Controls which report format the scan produces, enforcing that structured JSON output and a report file cannot be requested at the same time. 6 releases · 4 other sources · first seen Mar 2026

Also counts toward: CI/CD pipeline integration

release

  • Adds --output <dir> flag to direct --json, --sarif, and --sbom output files into a specified directory (created when missing); passing --output without one of those three flags is an error rather than a silent no-op.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.37.0 · Sep 2026 · source · release history
  • Adds a matching output input to the GitHub Action for the same directory-routing behaviour. v1.37.0 · Sep 2026 · source · release history
  • Adds --create-pr flag to cve-lite-cli that commits lockfile changes and opens a GitHub PR via gh after running with --fix v1.20.0 · Jun 2026 · source · release history
  • --sarif flag generates a SARIF 2.1.0 file for upload to GitHub Code Scanning v1.15.1 · May 2026 · source · release history
  • Introduces a reusable first-party GitHub Action for running CVE Lite CLI in GitHub Actions v1.2.0 · Apr 2026 · source · release history
  • Supports SARIF and JSON output formats suitable for CI pipelines and automation workflows. 1.0.2 · Mar 2026 · source · release history

docs

  • CLI cyber tool that scans JavaScript/TypeScript lockfiles for CVEs and outputs copy-and-run fix commands with parent-aware transitive remediation guidance.

command line

example

  • Produce SARIF for GitHub Code Scanning and an HTML report in one run. cve-lite scan --sarif --report v1.24.0 · Jun 2026 · source
  • Basic vulnerability scan cve-lite /path/to/project
CI/CD integration and workflow automation shipped Exposes CLI inputs in a GitHub Action workflow, supports custom SSL proxies, and enables scheduled automated security fix PRs with configurable branches and labels. 5 releases · 3 other sources · first seen Apr 2026

Also counts toward: CI/CD pipeline integration, Scheduled jobs

release

  • Adds delta input to the GitHub Action so pull requests receive a single upserted comment listing only the findings that PR introduced, not the full tree; fork PRs fall back to the job summary.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.40.0 · Oct 2026 · source · release history
  • Adds base-branch, labels, and token GitHub Action inputs for the fix PR workflow v1.26.0 · Jul 2026 · source · release history
  • GitHub Action gains a matching ca-cert input for corporate SSL proxy configuration v1.18.1 · May 2026 · source · release history
  • no-cache input added to the GitHub Action, defaulting to true in CI environments v1.15.1 · May 2026 · source · release history
  • Adds verbose and fail-on inputs to the GitHub Action workflow v1.2.0 · Apr 2026 · source · release history

docs

  • . Currently supports one key: The file must be a valid PEM certificate (starting with seen Aug 2026 · source

example

  • Enable automated security fix PRs for a bun repository on a schedule. name: Security Fixes on: schedule: - cron: '0 0 * * 1' jobs: cve-lite: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: owasp/cve-lite-cli@v1.26.0 with: fix: true create-pr: true… v1.26.0 · Jul 2026 · source
  • Run CVE Lite in CI and fail the build if high severity vulnerabilities are found. - uses: sonukapoor/cve-lite-cli@v1.2.0 with: verbose: "true" fail-on: high v1.2.0 · Apr 2026 · source
Scan completeness reporting shipped Reports any packages that could not be fully scanned so users know how complete the results are. 5 releases · 2 other sources · first seen Apr 2026

Also counts toward: CI/CD pipeline integration

release

  • --prod-only results can shift for Bun projects due to correct dev/prod classification v1.35.0 · Sep 2026 · source · release history
  • Adds --incomplete-policy warn|error flag (default: warn) to control exit behavior when detection data is incomplete; error exits with code 3. GitHub Action gains an incomplete-policy input. v1.32.0 · Sep 2026 · source · release history
  • Adds --incomplete-policy warn|error flag to control exit behavior when detection data is incomplete v1.32.0 · Sep 2026 · source · release history
  • Renders scan completeness in terminal output (compact and verbose modes) and in HTML reports, surfacing packument-fetch failures and other scan gaps. v1.29.0 · Aug 2026 · source · release history
  • Explicit skipped-item output introduced for urgent findings that cannot be fixed confidently v1.3.0 · Apr 2026 · source · release history

example

  • Write all structured output to a dedicated reports directory so a CI step can hand a stable path to the next stage without globbing or renaming. cve-lite /path/to/project --sarif --json --output reports v1.37.0 · Sep 2026 · source
  • Treat incomplete detection data as a hard error (exit 3) so CI pipelines never silently pass on partial results. cve-lite /path/to/project --incomplete-policy error v1.32.0 · Sep 2026 · source
SBOM inventory-only generation shipped Generates a pure dependency inventory without vulnerability data for diffing or attestation, excluding the vulnerability overlay. 2 releases · 2 other sources · first seen Sep 2026

release

  • Adds --sbom-inventory-only flag to generate an inventory-only document (no vulnerability overlay) for diffing and archival. v1.34.0 · Sep 2026 · source · release history
  • Adds --sbom-inventory-only flag to emit an SBOM without the vulnerability overlay, for diffing, archival and attestation workflows. v1.34.0 · Sep 2026 · source · release history

example

  • Produce a clean dependency inventory SBOM with no vulnerability data for diffing across CI runs or submitting for attestation without exposing finding details. cve-lite /path/to/project --sbom spdx --sbom-inventory-only v1.34.0 · Sep 2026 · source
  • Full fix plan with dependency paths cve-lite /path/to/project --verbose
Source-usage filtering in multi-folder scans shipped Applies source-usage filtering independently to each subfolder when scanning a multi-folder project, so only actively used dependencies are assessed in each context. 2 releases · 2 other sources · first seen Aug 2026

release

  • Extends --usage/--only-used flags to multi-folder scans: each subfolder now gets its own source-usage annotation and filtering, isolated from other subfolders (previously accepted but silently ignored outside single-folder mode). v1.29.0 · Aug 2026 · source · release history
  • --usage and --only-used now work in multi-folder scans (previously ignored), creating isolated source-usage annotations per subfolder v1.29.0 · Aug 2026 · source · release history

example

  • Audit a project for CVEs and copyleft/unknown licenses in one pass, failing CI on high-severity CVEs. cve-lite /path/to/project --check-licenses --fail-on high v1.32.0 · Sep 2026 · source
  • Filter JSON scan results to only the findings requiring immediate action — those the EPSS Priority Signal classifies as fix_now. cve-lite-cli scan | jq '[.[] | select(.prioritySignal == "fix_now")]' v1.33.0 · Sep 2026 · source
Private registry and dependency scope detection shipped Detects private registries across multiple package managers and automatically labels findings by direct/transitive hierarchy and dev/production scope. 3 releases · first seen Apr 2026

Also counts toward: Command-line interface

release

  • Private registry detection (⚠ Unverifiable (private source)) is now supported for pnpm (legacy and v9), Yarn Classic, and Bun lockfiles v1.22.0 · Jun 2026 · source · release history
  • Terminal output and HTML reports now show direct · dev / transitive · dev labels for findings from devDependencies, with Yarn Classic and Berry parsers updated to detect dev status v1.22.0 · Jun 2026 · source · release history
  • Adds --prod-only flag to filter out development dependencies when parsing lockfiles v1.6.0 · Apr 2026 · source · release history
PR delta rendering module shipped Provides a module to generate pull request comments that compare two scan reports for external tools and CI workflows. 2 releases · first seen Sep 2026

release

  • Adds the pr-delta-renderer module to the published package, enabling external tools to generate pull request comments that compare two scan reports v1.36.0 · Sep 2026 · source · release history
  • Publishes the PR delta renderer as part of the distributed package, enabling external tools and CI workflows outside this repository to generate pull request comments from two scan reports.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.36.0 · Sep 2026 · source · release history
Vulnerability scoring and advisory enrichment shipped suggested Enriches findings with FIRST.org EPSS scores and supplements OSV data with npm registry advisories to ensure comprehensive vulnerability coverage. 2 releases · first seen Sep 2026

Suggested capability: Vulnerability prioritization. This is our guess, not confirmed.

release

  • Enriches findings with FIRST.org EPSS scores after the OSV pass v1.32.0 · Sep 2026 · source · release history
  • Adds npm registry advisory API as a secondary source for packages with zero OSV matches v1.32.0 · Sep 2026 · source · release history
Release-cooldown awareness shipped Warns when a recommended fix version was released too recently to meet the configured minimum release-age threshold, across terminal, JSON, SARIF, and verbose output. 2 releases · first seen Jul 2026

Also counts toward: CI/CD pipeline integration, JSON data export

release

  • Surfaces release-cooldown warnings in SARIF output as properties.cooldownWarning on the result, making them visible in GitHub Code Scanning. v1.29.0 · Aug 2026 · source · release history
  • New cooldown-aware fix resolver reads min-release-age (npm .npmrc), minimumReleaseAge (pnpm), and npmMinimalAgeGate (yarn) and warns when a recommended fix version is newer than the configured release window; advisory only, on by default, no flag or exit-code change, renders in terminal, --verbose, JSON, and… v1.28.0 · Jul 2026 · source · release history
JSON output for override hygiene findings shipped Saves override hygiene findings to a timestamped JSON file in the same location as the main scan output, ready for ingestion into audit or SIEM systems. 1 release · 1 other source · first seen Jul 2026

Also counts toward: JSON data export

release

  • Adds overrides --json output written to a timestamped file, consistent with the main scan path. v1.27.0 · Jul 2026 · source · release history

example

  • Export override hygiene findings to a timestamped JSON file for ingestion into a SIEM or audit log. cve-lite /path/to/project overrides --json v1.27.0 · Jul 2026 · source
Ratchet baseline gating shipped Runs --ratchet against a committed baseline and exits non-zero when findings match the configured --fail-on gate, including when no baseline has been committed. 1 release · first seen Oct 2026

Also counts toward: Command-line interface

release

  • --ratchet with no committed baseline now applies --fail-on and exits non-zero when findings match the gate, instead of writing a baseline and exiting 0 — a CI job that checks out fresh every run and never committed its baseline could previously not fail and now can. v1.40.0 · Oct 2026 · source · release history
Compact output disclosure shipped When findings are withheld in compact output, the tool now states how many findings are hidden and which flags to run to reveal them, rather than truncating silently. 1 release · first seen Oct 2026

release

  • Compact output now discloses withheld findings and command groups with counts and instructions (e.g. Showing 3 of 53 findings. Run --verbose --all to see them all.) instead of silently truncating. v1.38.0 · Oct 2026 · source · release history
Configurable report output directory shipped Writes scan findings and reports to a user-specified directory, enabling deterministic file placement for CI/CD pipelines. 1 other source · first seen Sep 2026

Also counts toward: CI/CD pipeline integration

example

  • Write scan results to a specific directory for CI consumption cve-lite-scan --json --output ./reports/ v1.37.0 · Sep 2026 · source
Extended JSON output shipped Appends subfolder metadata to each finding in structured JSON output to support multi-folder and monorepo scan correlation. 1 release · first seen Jun 2026

Also counts toward: JSON data export

release

  • --json output now includes a subfolder field on each finding v1.19.0 · Jun 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for cve-lite-cli, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail cve-lite-cli puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

57 entries

  1. October 20262
  2. September 202611
  3. August 20267
  4. July 20263
  5. June 20267
  6. May 202610
  7. April 202614
  8. March 20263
    Show

    57 entries

    Project health

    Issue, contributor and maintainer activity in OWASP/cve-lite-cli, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 76 +76 vs prior 12 months
    2. Maintainers 3 +3 joined · −0 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 3% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 5.6 hours
    6. Open backlog 28 of 529 issues ever filed
    1. Issues opened / month 2 · 27 communitymaintainers
    2. Open backlog 28
    3. Contributors / month 17
    4. Commits / month 75
    5. Stars 694
    Issue themes, last 12 months
    • bugs 20%
    • features 34%
    • docs 23%
    • other 23%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →