cve-lite-cli 1.26.0 → 1.27.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,4 +1,6 @@
1
1
 
2
+ *Most tools tell you what's wrong. CVE Lite CLI tells you what to run.*
3
+
2
4
  [![OWASP Lab Project](https://img.shields.io/badge/OWASP-Lab%20Project-48A646?logo=owasp)](https://owasp.org/cve-lite-cli)
3
5
  [![npm version](https://img.shields.io/npm/v/cve-lite-cli)](https://www.npmjs.com/package/cve-lite-cli)
4
6
  [![npm downloads](https://img.shields.io/npm/dm/cve-lite-cli)](https://www.npmjs.com/package/cve-lite-cli)
@@ -25,9 +27,14 @@
25
27
 
26
28
  <table>
27
29
  <tr>
28
- <td align="center" width="33%"><p>🏆</p><strong>OWASP Lab Project</strong><br/><sub>Peer-reviewed by the org behind the OWASP Top 10 —<br/>the security standard followed by millions of developers</sub></td>
29
- <td align="center" width="33%"><p>🎯</p><strong>Remediation-first</strong><br/><sub>Validated fix commands + parent-aware<br/>transitive guidance — not just CVE IDs</sub></td>
30
- <td align="center" width="33%"><p>🔒</p><strong>Runs locally</strong><br/><sub>Nothing leaves your machine — not your<br/>code, not your dependency tree</sub></td>
30
+ <td align="center" width="33%">🏆</td>
31
+ <td align="center" width="33%">🎯</td>
32
+ <td align="center" width="33%">🔒</td>
33
+ </tr>
34
+ <tr>
35
+ <td align="center" width="33%" valign="top"><strong>OWASP Lab Project</strong><br/><sub>Peer-reviewed by the org behind the OWASP Top 10 —<br/>the security standard followed by millions of developers</sub></td>
36
+ <td align="center" width="33%" valign="top"><strong>Remediation-first</strong><br/><sub>Validated fix commands + parent-aware<br/>transitive guidance — not just CVE IDs</sub></td>
37
+ <td align="center" width="33%" valign="top"><strong>Runs locally</strong><br/><sub>Nothing leaves your machine — not your<br/>code, not your dependency tree</sub></td>
31
38
  </tr>
32
39
  </table>
33
40
 
@@ -64,24 +71,6 @@
64
71
 
65
72
  ---
66
73
 
67
- ## The problem with how security scanning works today
68
-
69
- Most security tooling is designed around pipelines, not people.
70
-
71
- Dependabot files PRs you'll get to eventually. CI scanners block merges hours after the fact. Security dashboards surface a list of CVE IDs with no clear path to resolving them. By the time a developer is looking at a scan result, the code has already been reviewed and is waiting to ship.
72
-
73
- The feedback loop is too slow to be useful, and too noisy to be trusted. Developers learn to ignore it.
74
-
75
- There is also a more fundamental problem: these tools tell you what is vulnerable. Very few tell you what to actually do about it. The result is a gap between detection and remediation that security teams paper over with manual triage, and developers experience as alert fatigue.
76
-
77
- ## A different model
78
-
79
- CVE Lite CLI is built around a different idea: **vulnerability scanning belongs at the developer's terminal, not at the end of a pipeline.**
80
-
81
- It reads your lockfile locally, queries [OSV](https://osv.dev) for advisory data, and produces a concrete remediation plan — not a list of identifiers. You get copy-and-run `npm install`, `pnpm add`, `yarn add`, or `bun add` commands scoped to your package manager. You see exactly which packages are directly installed versus pulled in transitively. You can scan with no internet connection in restricted-network environments.
82
-
83
- The tool is designed for the moment right before you push: fast, honest, and actionable.
84
-
85
74
  ## Quick start
86
75
 
87
76
  ```bash
@@ -97,18 +86,50 @@ npx cve-lite-cli /path/to/project
97
86
 
98
87
  No account. No configuration. No source code leaves your machine.
99
88
 
100
- ## What it does
89
+ ## Usage
90
+
91
+ ```bash
92
+ cve-lite /path/to/project # basic scan
93
+ cve-lite /path/to/project --verbose # full fix plan with dependency paths
94
+ cve-lite /path/to/project --fix # apply validated direct fixes and rescan
95
+ cve-lite /path/to/project --fail-on high # exit non-zero on high severity and above
96
+ cve-lite /path/to/project --json # JSON output
97
+ cve-lite /path/to/project --sarif # SARIF output for GitHub Code Scanning
98
+ cve-lite /path/to/project --report # interactive HTML dashboard
99
+ cve-lite /path/to/project --check-overrides # audit override hygiene alongside the CVE scan
100
+ cve-lite advisories sync # sync advisory DB for offline use
101
+ cve-lite /path/to/project --offline # scan with no runtime API calls
102
+ ```
103
+
104
+ For the full flag reference and exit codes see the [CLI Reference guide](https://owasp.org/cve-lite-cli/docs/cli-reference) and [Fix mode guide](https://owasp.org/cve-lite-cli/docs/fix-mode).
105
+
106
+ ## Override hygiene (`overrides`)
101
107
 
102
- - **Produces copy-and-run fix commands** — every finding comes with a package-manager-aware install command you can run immediately
103
- - **Distinguishes direct from transitive risk** — shows whether the vulnerability is in something you installed or buried three levels deep in a dependency chain
104
- - **Explains parent update paths** — for transitive npm findings, recommends `npm update <parent>` when the current parent range can resolve a known non-vulnerable child, or a parent upgrade when the range itself must change
105
- - **Usage-aware reachability** — optionally uses static analysis to detect whether vulnerable packages are actually imported in your code, cutting noise with `--usage` and `--only-used`
106
- - **Offline advisory DB** — sync advisory data ahead of time and scan with zero runtime API calls, designed for enterprise and air-gapped environments
107
- - **Interactive HTML report** — generate a self-contained dashboard with severity cards, a searchable findings table, and copy-ready fix commands (`--report`)
108
- - **Auto-fix mode** — apply validated direct dependency fixes and rescan automatically (`--fix`)
109
- - **Override hygiene checks** — audit npm/pnpm/yarn/bun `overrides` and `resolutions` for orphaned targets, floating tags, surpassed pins, ineffective nested overrides, and platform-binary coupling (`--check-overrides`, rules `OA001`-`OA008`)
110
- - **CI-ready** — `--fail-on high` exits non-zero on findings at or above a severity threshold; a first-party [GitHub Action](https://github.com/marketplace/actions/cve-lite-cli) is available on the Marketplace; `--sarif` writes SARIF 2.1.0 output for direct upload to GitHub Code Scanning; `--cdx` writes a CycloneDX 1.4 SBOM for Dependency-Track and compliance artifacts; `--json` integrates with SIEM tools and dashboards
111
- - **Minimal footprint** — four runtime dependencies, intentionally kept small for a security tool
108
+ `overrides` and `resolutions` are powerful, but they rot. CVE Lite CLI audits them across npm, pnpm, yarn, and bun, catching eleven classes of problem:
109
+
110
+ | Rule | What it catches |
111
+ |---|---|
112
+ | `OA001` | Orphaned target: override for a package no longer in the tree |
113
+ | `OA002` | Floating tag: override pinned to a moving tag (`latest`, `next`) |
114
+ | `OA003` | Wrong section: override placed in the wrong container |
115
+ | `OA004` | Surpassed pin: the rest of the tree has moved past the pin |
116
+ | `OA005` | Nested ineffective override that never applies |
117
+ | `OA006` | Coupled platform binary: override fights a parent's exact pin |
118
+ | `OA007` | Frozen latest: registry has drifted past the pinned version (needs `--check-network`) |
119
+ | `OA008` | Materialized vulnerable copy still on disk despite the override |
120
+ | `OA009` | Stale floor: override range floor already met by all parent declarations |
121
+ | `PD001` | Override-only phantom: package imported in source but only present via an override pin |
122
+ | `PD002` | Transitive-only phantom: package imported in source but only present as a transitive dependency |
123
+
124
+ Use the `overrides` subcommand for a hygiene-only run (no CVE scan, faster, fully offline-capable) with auto-fix support. Use `--check-overrides` to append hygiene results to a regular CVE scan in one pass.
125
+
126
+ ```bash
127
+ cve-lite /path/to/project overrides # hygiene only - no CVE scan
128
+ cve-lite /path/to/project overrides --fix # hygiene only, auto-fix where possible
129
+ cve-lite /path/to/project --check-overrides # CVE scan + hygiene in one pass
130
+ ```
131
+
132
+ For the full guide with per-rule examples and CI patterns, see the [Override Hygiene Auditing guide](https://owasp.org/cve-lite-cli/docs/override-hygiene).
112
133
 
113
134
  ## What it looks like
114
135
 
@@ -144,37 +165,13 @@ No account. No configuration. No source code leaves your machine.
144
165
  </p>
145
166
  </details>
146
167
 
147
- ## Workflow integration
148
-
149
- CVE Lite CLI fits at every stage of the development workflow, not just CI.
168
+ ## Why CVE Lite CLI
150
169
 
151
- **Local development** — run a scan before opening a PR. The default output is fast and minimal. `--verbose` adds the full fix plan with dependency paths and prioritized remediation commands. `--report` opens an interactive HTML dashboard.
170
+ Most security tooling is built around pipelines, not developers. Dependabot opens PRs you'll get to eventually. CI scanners block merges after the fact. Dashboards surface lists of CVE IDs with no clear path to fixing them. Developers learn to ignore it.
152
171
 
153
- **CI pipelines** — use `--fail-on high` to gate builds on severity. JSON output (`--json`) integrates with SIEM, dashboards, and custom automation. SARIF output (`--sarif`) writes a SARIF 2.1.0 file for direct upload to GitHub Code Scanning — findings appear in the Security tab and annotate PRs.
172
+ CVE Lite CLI is built for the moment before you push. It reads your lockfile locally, queries [OSV](https://osv.dev), and produces copy-and-run `npm install`, `pnpm add`, `yarn add`, or `bun add` commands — not a list of identifiers. You see which packages are direct versus transitive, get parent-aware upgrade guidance, and can scan offline in restricted environments.
154
173
 
155
- **Restricted and enterprise environments** — sync the advisory database ahead of time with `cve-lite advisories sync`, then scan offline with `--offline`. No runtime outbound calls during the scan. Syncing ~217,065 advisory records completes in under 9 seconds.
156
-
157
- **GitHub Actions** — a first-party action is available on the Marketplace:
158
-
159
- ```yaml
160
- - uses: OWASP/cve-lite-cli@v1
161
- with:
162
- verbose: "true"
163
- fail-on: high
164
- sarif: "true"
165
-
166
- - name: Upload to GitHub Code Scanning
167
- uses: github/codeql-action/upload-sarif@v4
168
- if: always()
169
- with:
170
- sarif_file: ${{ github.workspace }}
171
- ```
172
-
173
- > **Note:** `if: always()` is required on the upload step. Without it, the upload is skipped when `--fail-on` exits non-zero — losing your findings in Code Scanning exactly when they matter most.
174
-
175
- CVE Lite CLI scans its own dependencies in CI. See [`self-scan.yml`](https://github.com/OWASP/cve-lite-cli/blob/main/.github/workflows/self-scan.yml).
176
-
177
- For full CI patterns including offline workflows, git hooks, and scripted automation, see the [CI and Workflow Integration guide](https://owasp.org/cve-lite-cli/docs/workflow-integration).
174
+ The closer a security tool is to a developer's natural workflow, the more likely it is to be used.
178
175
 
179
176
  ## How it compares
180
177
 
@@ -203,303 +200,93 @@ No other free tool combines all of the following: lockfile scanning across npm,
203
200
 
204
201
  The transitive parent guidance is a key difference: CVE Lite CLI avoids recommending direct installs for packages that are only present transitively. For npm lockfiles, it can identify when `npm update <parent>` is enough to re-resolve a known non-vulnerable child within the current parent range, and when the parent package itself needs an upgrade.
205
202
 
206
- ### About Socket CLI
207
- Socket provides deep supply-chain analysis (malware, typosquatting, maintainer risk) but requires a paid account for full features. CVE Lite CLI remains one of the few fully free, offline, and account-free options with strong transitive analysis.
208
-
209
203
  For detailed per-tool analysis, see [Comparison with other tools](https://owasp.org/cve-lite-cli/docs/comparison).
210
204
 
211
- ## Real-world validation
212
-
213
- CVE Lite CLI has been evaluated against real open-source projects to verify that it surfaces meaningful issues — including non-obvious transitive vulnerabilities and complex upgrade paths — not just low-signal advisory matches.
214
-
215
- - [OWASP Juice Shop](https://owasp.org/cve-lite-cli/docs/case-studies/owasp-juice-shop) — scanning a deliberately vulnerable application with known dependency issues
216
- - [NestJS](https://owasp.org/cve-lite-cli/docs/case-studies/nestjs) — working through a real transitive dependency remediation sequence across a widely-used Node.js framework
217
- - [Analog](https://owasp.org/cve-lite-cli/docs/case-studies/analog) — scanning a modern pnpm v9 Angular monorepo (3,367 packages) with unexpected toolchain vulnerabilities
218
- - [Ghost](https://owasp.org/cve-lite-cli/docs/case-studies/ghost) — 26 vulnerable packages across 4,447 resolved in a professionally maintained CMS — every one transitive, including a critical XSS in the library responsible for making user content safe
219
- - [Astro](https://owasp.org/cve-lite-cli/docs/case-studies/astro) — verified baseline scan of a modern pnpm monorepo (2,228 packages, 34 findings at revision `221bb4b`) with a critical transitive SDK chain and four generated fix command groups
220
- - [Turborepo](https://owasp.org/cve-lite-cli/docs/case-studies/turborepo) — verified baseline scan of a build-system pnpm monorepo (1,776 packages, 13 findings at revision `c85d410`) with a critical no-fix sandbox beta, all-transitive risk, and zero auto-generated fix commands on this snapshot
221
- - [Visual Studio Code](https://owasp.org/cve-lite-cli/docs/case-studies/vscode) — verified baseline scan of the VS Code root npm lockfile (1,374 packages, 9 findings at revision `bc678ca`) with two direct Anthropic SDK advisories, a high-severity gulp toolchain chain, and two generated fix command groups
222
- - [Gatsby](https://owasp.org/cve-lite-cli/docs/case-studies/gatsby) — verified baseline scan of a Yarn Classic monorepo (3,568 packages, 128 findings at revision `1f38c85`) with five direct findings, critical transitive template-engine chains, and CVE Lite vs `yarn audit` deduplication
223
- - [Vercel AI SDK](https://owasp.org/cve-lite-cli/docs/case-studies/vercel-ai-sdk) — verified baseline scan of the [vercel/ai](https://github.com/vercel/ai) pnpm monorepo (3,570 packages, 55 findings at revision `3215032`) with three direct findings (`next`, `turbo`) and five workspace-scoped fix command groups — distinct from the Turborepo snapshot
224
- - [Mastra](https://owasp.org/cve-lite-cli/docs/case-studies/mastra) — verified baseline scan of an AI agent framework pnpm monorepo (4,555 packages, 64 findings at revision `e9d54b2`) with four direct findings, two command groups, and workspace-scoped `pnpm add --filter playground` fixes
225
- - [Lit](https://owasp.org/cve-lite-cli/docs/case-studies/lit) — verified baseline scan of an npm workspaces monorepo (2,059 packages, 99 findings at revision `20afabd`) with three direct `rollup` majors and workspace-scoped upgrade commands (13 first-pass fixes, 4 command groups)
226
- - [LangChain.js](https://owasp.org/cve-lite-cli/docs/case-studies/langchainjs) — verified baseline scan of a pnpm LLM-framework monorepo (2,174 packages, 13 findings at revision `1503c9b`) with a lean-graph profile, three high-severity findings with validated fix targets, and a malicious-package advisory on OpenSearch integration paths
227
- - [OpenAI Agents SDK (JavaScript)](https://owasp.org/cve-lite-cli/docs/case-studies/openai-agents-js) — verified baseline scan of a pnpm AI-agent monorepo (1,683 packages, 31 findings at revision `f76fc19`) with 0 direct findings, MCP/Daytona parent clusters, and one generated `verdaccio` parent-upgrade command
228
- - [n8n](https://owasp.org/cve-lite-cli/docs/case-studies/n8n) — verified baseline scan of a workflow automation pnpm monorepo (3,746 packages, 32 findings at revision `e2e0394`) with one direct `turbo` fix, four command groups, and email/editor transitive clusters
229
- - [CamoFox Browser](https://owasp.org/cve-lite-cli/docs/case-studies/camofox-browser) — verified baseline scan of an AI agent browser automation npm graph (435 packages, 2 findings at revision `ce3a3b0`) with dual `qs` fix strategies — within-range `npm update qs` and parent `npm install express@4.22.2`
230
- - [Storybook](https://owasp.org/cve-lite-cli/docs/case-studies/storybook) — verified baseline scan of a Yarn Berry monorepo (3,008 packages, 92 findings at revision `cc19ae1`) spanning cross-framework sandbox templates, five critical transitive chains, and one direct vite fix command
231
- - [Twenty](https://owasp.org/cve-lite-cli/docs/case-studies/twenty) — verified baseline scan of an open-source CRM Yarn Berry monorepo (5,451 packages, 105 findings at revision `fc90b4b`) with 0 direct findings, six critical test-stack chains, and four Nx parent-upgrade command groups
232
- - [Strapi](https://owasp.org/cve-lite-cli/docs/case-studies/strapi) — verified baseline scan of a headless CMS Yarn Berry monorepo (2,887 packages, 18 findings) with two direct findings (`lodash`, `qs`) and mixed transitive remediation paths
233
- - [Payload CMS](https://owasp.org/cve-lite-cli/docs/case-studies/payload) — verified baseline scan of a TypeScript-first headless CMS pnpm monorepo (2,602 packages, 18 findings) with one direct finding and workspace-scoped fix commands
234
- - [Presenton](https://owasp.org/cve-lite-cli/docs/case-studies/presenton) — verified baseline scan of an AI presentation generator with dual npm lockfiles (root + Electron shell), demonstrating multi-lockfile coverage across 9 findings
235
-
236
- In-repo lockfile fixtures for Astro, Turborepo, Visual Studio Code, Gatsby, Vercel AI SDK, Mastra, Lit, LangChain.js, OpenAI Agents JS, n8n, CamoFox Browser, Storybook, Twenty, Strapi, Payload CMS, and Presenton live under [`examples/`](examples/readme.md) — clone the repo and scan immediately without downloading full upstream checkouts.
237
-
238
- These are not demos. They are documented scans against real codebases with real findings, recorded before and after applying fix commands.
239
-
240
- If you maintain an open-source JavaScript or TypeScript project and want CVE Lite CLI evaluated on it, open an issue and share the repository. Strong candidates may be turned into future public case studies.
241
-
242
- ## Press
243
-
244
- - **[Sniff out stale AI override advice with this open source CLI](https://www.theregister.com/security/2026/06/23/sniff-out-stale-ai-override-advice-with-this-open-source-cli/5259853)** — The Register (Thomas Claburn, Senior Reporter), June 2026
245
- - **[OWASP Adopts CVE Lite CLI to Boost Dependency Scanning](https://devops.com/owasp-adopts-cve-lite-cli-to-boost-dependency-scanning/)** — DevOps.com, May 2026
246
- - **[CVE Lite CLI repère les dépendances à risque](https://www.lemondeinformatique.fr/actualites/lire-cve-lite-cli-repere-les-dependances-a-risque-100270.html)** — Le Monde Informatique (France), May 2026
247
- - **[Lieferketten-Angriff: 5.500 GitHub-Repos in 6 Stunden kompromittiert](https://www.ad-hoc-news.de/wissenschaft/lieferketten-angriff-5-500-github-repos-in-6-stunden-kompromittiert/69418833)** — ad-hoc-news (Germany), May 2026 (references CVE Lite CLI)
248
- - **[AIがコーディングを加速する中、CVE Lite CLIはセキュリティを意図的にAI無しに保つ](https://blackhatnews.tokyo/archives/104903)** — TokyoBlackHatNews (Japan), May 2026
249
- - **[The postcss That Would Not Die, and How CVE Lite Ended My Override Grind](https://labs.hexaxia.tech/blog/hexops-cve-lite-integration/)** — Hexaxia Labs (Aaron Lamb), May 2026
250
- - **[As AI speeds coding, CVE Lite CLI keeps security deliberately AI-free](https://www.csoonline.com/article/4176701/as-ai-speeds-coding-cve-lite-cli-keeps-security-deliberately-ai-free.html)** — CSO Online (Shweta Sharma), May 2026
251
- - **[CVE Lite CLI: The Dependency Scanner That Actually Tells You What to Run](https://medium.com/@techlatest.net/cve-lite-cli-the-dependency-scanner-that-actually-tells-you-what-to-run-not-just-whats-broken-f6b518199981)** — Medium (TechLatest.Net), May 2026
252
- - **[AI Security Is Changing Fast — These 6 Open-Source Tools Prove It](https://medium.com/@techlatest.net/ai-security-is-changing-fast-these-6-open-source-tools-prove-it-5c5c9081cff7)** — Medium (TechLatest.Net), May 2026
253
- - **[Hottest cybersecurity open-source tools of the month: May 2026](https://www.helpnetsecurity.com/2026/05/28/hottest-cybersecurity-open-source-tools-of-the-month-may-2026/)** — Help Net Security Monthly Roundup, May 2026
254
- - **[CVE Lite CLI: Open-source dependency vulnerability scanner](https://www.helpnetsecurity.com/2026/05/20/cve-lite-cli-open-source-dependency-vulnerability-scanner/)** — Help Net Security, May 2026
255
- - **[Review of CVE Lite CLI](https://developmentcurated.com/testing-and-security/review-of-cve-lite-cli/)** — Development Curated (Sebastian Raiffen, IT Security Consultant), April 2026
256
-
257
- ## Recognized by OWASP
258
-
259
- OWASP (Open Web Application Security Project) is the globally recognized nonprofit behind the security standards followed by millions of developers worldwide — most notably the [OWASP Top 10](https://owasp.org/www-project-top-ten/), the most widely cited web application security reference in the industry. Organizations from startups to Fortune 500 companies use OWASP guidelines as the foundation of their security programs.
260
-
261
- CVE Lite CLI is an [OWASP Lab Project](https://owasp.org/cve-lite-cli) — reviewed and accepted by the OWASP community as a vendor-neutral, open source security tool. Being part of OWASP means:
262
-
263
- - **Peer-reviewed** by security professionals
264
- - **Community-driven** development and governance
265
- - **Vendor-neutral** with no commercial platform required
266
- - **Open source** with transparent security practices and a minimal dependency footprint
267
-
268
- **Where it fits in the OWASP ecosystem:**
269
-
270
- CVE Lite CLI fills a specific gap — fast, local-first JS/TS dependency scanning close to release time — that broader OWASP tools are not optimized for:
271
-
272
- | Tool | Focus |
273
- |---|---|
274
- | CVE Lite CLI | Lockfile-first, local developer CLI, remediation-focused, JS/TS |
275
- | OWASP Dependency-Check | Multi-language, SAST-style, broader ecosystem |
276
- | OWASP dep-scan | Multi-language and environment, SBOM and cloud-native |
277
- | OWASP Dependency-Track | Platform and SBOM management, not a local CLI |
278
-
279
- CVE Lite CLI complements these tools. It is not a replacement for continuous monitoring or full SBOM management — it is the fast local check you run before pushing.
280
-
281
- ## Philosophy
282
-
283
- Security tooling has optimized heavily for breadth of detection and compliance reporting. That is useful at the platform level. It is the wrong model for the individual developer trying to ship clean code before end of day.
284
-
285
- Detection without remediation creates work without resolution. A vulnerability report that ends with a list of CVE IDs shifts the burden entirely onto the developer: look up each advisory, figure out which version is safe, work out whether it is a direct or transitive dependency, and construct the right install command by hand. That friction is why security findings go unresolved.
286
-
287
- CVE Lite CLI is built on the premise that **the closer a security tool is to the developer's natural workflow, the more likely it is to be used** — and that a tool that surfaces a problem alongside the fix is more valuable than one that only surfaces the problem.
288
-
289
- ## What's next
290
-
291
- The CLI is the foundation. The model — local-first, actionable, developer-native — extends naturally beyond the terminal.
292
-
293
- JSON and SARIF outputs make findings consumable by editors, dashboards, and automated workflows today. The next phase of the project is oriented around tighter developer integration: surfacing vulnerabilities at the point of dependency installation, not just at scan time; deeper IDE integration; and team-level visibility without requiring a cloud platform.
294
-
295
- See the [Roadmap](https://owasp.org/cve-lite-cli/docs/roadmap) for the current plan.
296
-
297
- ## Usage
298
-
299
- ```bash
300
- # Basic scan
301
- cve-lite /path/to/project
302
-
303
- # Show all findings
304
- cve-lite /path/to/project --all
305
-
306
- # Focus on urgent findings only
307
- cve-lite /path/to/project --min-severity high
308
-
309
- # Full output: fix plan, paths, and complete table
310
- cve-lite /path/to/project --verbose
311
-
312
- # Apply validated direct dependency fixes and rescan
313
- cve-lite /path/to/project --fix
314
-
315
- # Audit override hygiene (OA001-OA008) across npm/pnpm/yarn/bun
316
- cve-lite /path/to/project --check-overrides
317
-
318
- # Audit and auto-clean stale or ineffective overrides
319
- cve-lite /path/to/project --check-overrides --fix
320
-
321
- # Production dependencies only (where supported by the lockfile)
322
- cve-lite /path/to/project --prod-only
323
-
324
- # Fail a build on high severity and above
325
- cve-lite /path/to/project --fail-on high
326
-
327
- # JSON output
328
- cve-lite /path/to/project --json
329
-
330
- # SARIF output for GitHub Code Scanning and other SARIF-compatible tools
331
- cve-lite /path/to/project --sarif
332
-
333
- # Generate an HTML vulnerability dashboard (opens in browser automatically)
334
- cve-lite /path/to/project --report
335
- cve-lite /path/to/project --report ./my-report --no-open
336
-
337
- # Scan project source files to check if vulnerable dependencies are actually imported
338
- cve-lite /path/to/project --usage
339
-
340
- # Filter out noise by only showing vulnerabilities in packages that are imported in your source code
341
- cve-lite /path/to/project --usage --only-used
342
-
343
- # Sync the local advisory DB for offline scans
344
- cve-lite advisories sync
345
-
346
- # Scan with zero runtime advisory API calls
347
- cve-lite /path/to/project --offline
205
+ ## Replace Dependabot with one batched PR
348
206
 
349
- # Use a specific local advisory DB file
350
- cve-lite /path/to/project --offline-db /path/to/advisories.db
207
+ CVE Lite CLI v1.26.0 ships a GitHub Action fix mode that runs on a schedule and opens a **single batched pull request** with all validated dependency upgrades - advisory IDs, before/after finding counts, and OSV-confirmed fix versions included.
351
208
 
352
- # Use a custom advisory endpoint
353
- cve-lite /path/to/project --osv-url https://security.company.internal/osv
209
+ Add this file to your repo:
354
210
 
355
- # Allow custom endpoint to resolve to private/reserved IPs (for internal mirrors)
356
- cve-lite /path/to/project --osv-url https://internal-mirror.company.local/osv --allow-private-osv-url
357
-
358
- # Show version
359
- cve-lite --version
360
-
361
- # Install AI assistant skill files for Claude Code, Codex CLI, Gemini CLI, Cursor, and GitHub Copilot
362
- cve-lite install-skill
363
- ```
364
-
365
- ### Why is `--usage` an opt-in flag?
366
-
367
- CVE Lite CLI is designed to be fast. Scanning a lockfile is nearly instantaneous, whereas running static reachability analysis across thousands of source files takes significantly more time. Static analysis can also produce false negatives when packages are used in build scripts or dynamically imported at runtime. Making `--usage` opt-in ensures the default lockfile scan remains instant and strictly reflects your dependency graph, while giving you the option to aggressively filter out unreachable noise when triaging findings.
368
-
369
- ## Auto-fix mode (`--fix`)
370
-
371
- `--fix` applies validated direct dependency fixes using your project's package manager, then rescans automatically.
372
-
373
- In the current version it:
374
- - applies only direct dependency fixes with a validated lowest known non-vulnerable target
375
- - uses `npm install`, `pnpm add`, `yarn add`, or `bun add` based on your lockfile
376
- - rescans automatically after applying fixes
377
- - when combined with `--check-overrides`, also runs the override hygiene fix-and-verify hook after the CVE fixes: it applies fixable override findings, then re-audits the just-touched packages (`OA001`/`OA008`) to confirm no vulnerable copy is still nested under a parent dependency. Without `--check-overrides`, `--fix` only touches CVE fixes and never modifies your `overrides`
378
- - does **not** auto-apply transitive overrides or guarantee application compatibility
379
-
380
- ```bash
381
- npx cve-lite-cli /path/to/project --fix
382
- ```
383
-
384
- **Exit codes.** `--fix` adds a dedicated exit code for a verify failure, so CI can tell "nothing to fix" apart from "the fix ran but did not take":
385
-
386
- | Code | Meaning |
387
- |---|---|
388
- | `0` | no findings at or above `--fail-on` |
389
- | `1` | findings present (CVE or override) at or above `--fail-on` |
390
- | `2` | `--fix` applied but the post-fix verify pass detected the fix did not take |
391
- | `3` | tool error (unreadable lockfile, unhandled exception) |
392
-
393
- See the [Fix mode guide](https://owasp.org/cve-lite-cli/docs/fix-mode) for output details and interpretation.
394
-
395
- For a deeper explanation of how the CLI chooses direct upgrades, parent upgrades, and npm `update` recommendations for transitive findings, see the [Remediation Strategy guide](https://owasp.org/cve-lite-cli/docs/remediation-strategy).
396
-
397
- ## Override hygiene (`overrides`)
398
-
399
- `overrides` and `resolutions` are powerful, but they rot. A pin you added to dodge a CVE last year can outlive its target, drift behind upstream, or quietly stop taking effect after a refactor, leaving a vulnerable copy still nested under a parent dependency. `--check-overrides` audits that hygiene across npm, pnpm, yarn, and bun, reporting eight classes of problem (`OA001`-`OA008`):
400
-
401
- | Rule | What it catches |
402
- |---|---|
403
- | `OA001` | Orphaned target: override for a package no longer in the tree |
404
- | `OA002` | Floating tag: override pinned to a moving tag (`latest`, `next`) |
405
- | `OA003` | Wrong section: override placed in the wrong container |
406
- | `OA004` | Surpassed pin: the rest of the tree has moved past the pin |
407
- | `OA005` | Nested ineffective override that never applies |
408
- | `OA006` | Coupled platform binary: override fights a parent's exact pin |
409
- | `OA007` | Frozen latest: registry has drifted past the pinned version (needs `--check-network`) |
410
- | `OA008` | Materialized vulnerable copy still on disk despite the override |
411
-
412
- ```bash
413
- # Audit, severity-grouped terminal output
414
- cve-lite /path/to/project --check-overrides
415
-
416
- # Structured JSON findings
417
- cve-lite /path/to/project --check-overrides --json
418
-
419
- # Apply RFC 6902 patches for fixable findings
420
- cve-lite /path/to/project --check-overrides --fix
421
-
422
- # Scope a run (or a fix) to a single rule
423
- cve-lite /path/to/project --check-overrides --rule OA001
424
-
425
- # Enable the OA007 registry drift check (opt-in network)
426
- cve-lite /path/to/project --check-overrides --check-network
427
-
428
- # Stream an NDJSON change-control log of every detection and fix
429
- cve-lite /path/to/project --check-overrides --audit-log ./override-audit.ndjson
430
- ```
431
-
432
- `--fix` applies fixes as RFC 6902 patches to `package.json`. A chokepoint guard means a fix can only remove, repin, move, or relocate an existing override; it can never invent a new override key. Suggest-only findings (OA004 cross-major, OA005.d/.e, all of OA008) and "proposed" fixes (the OA006 relocate floor) carry no auto-applied patch and are surfaced as recommendations. `--fail-on <severity>` sets the minimum severity that makes the command exit non-zero (default: `critical`).
433
-
434
- For the full guide with diagrams, per-rule examples, and CI patterns, see the [Override Hygiene Auditing guide](https://owasp.org/cve-lite-cli/docs/override-hygiene). Full per-rule reference including OA005 sub-codes lives in [`docs/rules/`](docs/rules/README.md). For the programmatic API, see [`docs/api/overrides.md`](docs/api/overrides.md).
435
-
436
- ## AI assistant integration (`install-skill`)
437
-
438
- CVE Lite CLI can teach your AI coding assistant how to analyze scan results and produce a prioritized remediation plan. Run this once in your project root:
439
-
440
- ```bash
441
- cve-lite install-skill
211
+ ```yaml
212
+ # .github/workflows/cve-lite-fix.yml
213
+ name: CVE Lite security fixes
214
+ on:
215
+ schedule:
216
+ - cron: '0 6 * * 1' # every Monday at 6am
217
+ workflow_dispatch:
218
+ permissions:
219
+ contents: write
220
+ pull-requests: write
221
+ jobs:
222
+ fix:
223
+ runs-on: ubuntu-latest
224
+ steps:
225
+ - uses: actions/checkout@v4
226
+ with:
227
+ ref: ${{ github.event.repository.default_branch }}
228
+ - uses: OWASP/cve-lite-cli@v1
229
+ with:
230
+ fix: 'true'
231
+ create-pr: 'true'
442
232
  ```
443
233
 
444
- This writes skill files for Claude Code, Codex CLI, Gemini CLI, Cursor, and GitHub Copilot into the current directory. Commit them so every developer on your team gets the context automatically.
445
-
446
- Once installed, the workflow is:
234
+ | | Dependabot | CVE Lite fix mode |
235
+ |---|---|---|
236
+ | PRs per run | One per package | One batched PR |
237
+ | Advisory IDs in PR body | No | Yes (GHSA-xxxx, CVE-xxxx) |
238
+ | Fix version validated against OSV | No | Yes |
239
+ | Before/after finding counts | No | Yes |
240
+ | pnpm / Yarn Berry / Bun | Limited | Full native support |
241
+ | OWASP recognition | No | OWASP Lab Project |
447
242
 
448
- ```bash
449
- # 1. Scan and save results to a JSON file
450
- cve-lite . --json
451
-
452
- # 2. Ask your AI assistant to analyze findings
453
- # In Claude Code: /cve-lite
454
- # In other tools: the skill is picked up automatically
455
- ```
243
+ [Full Action documentation ->](https://owasp.org/cve-lite-cli/docs/github-action) - for scan-only CI gating see the [CI and Workflow Integration guide](https://owasp.org/cve-lite-cli/docs/workflow-integration).
456
244
 
457
- The AI assistant reads the JSON output, prioritizes findings by severity and relationship, checks whether vulnerable packages are actually imported in your source code, and produces a concrete remediation plan with the exact commands to run.
458
-
459
- See the [AI Assistant Integration guide](https://owasp.org/cve-lite-cli/docs/ai-assistant-integration) for the full workflow and what the skill teaches the assistant.
245
+ ## Real-world validation
460
246
 
461
- ## HTML vulnerability report (`--report`)
247
+ CVE Lite CLI has been evaluated against real open-source projects to verify that it surfaces meaningful issues - including non-obvious transitive vulnerabilities and complex upgrade paths - not just low-signal advisory matches.
462
248
 
463
- Generate a self-contained HTML dashboard from any scan — severity cards, an interactive findings table with search, copy-ready fix commands, and breaking-change indicators on upgrades — all written to a local directory and opened automatically in your browser.
249
+ - [OWASP Juice Shop](https://owasp.org/cve-lite-cli/docs/case-studies/owasp-juice-shop) - scanning a deliberately vulnerable application with known dependency issues
250
+ - [NestJS](https://owasp.org/cve-lite-cli/docs/case-studies/nestjs) - working through a real transitive dependency remediation sequence across a widely-used Node.js framework
251
+ - [Visual Studio Code](https://owasp.org/cve-lite-cli/docs/case-studies/vscode) - two direct Anthropic SDK advisories and a high-severity gulp toolchain chain in the VS Code root lockfile
252
+ - [Gatsby](https://owasp.org/cve-lite-cli/docs/case-studies/gatsby) - Yarn Classic monorepo with 128 findings, five direct CVEs, and CVE Lite vs `yarn audit` deduplication
253
+ - [Analog](https://owasp.org/cve-lite-cli/docs/case-studies/analog) - modern pnpm Angular monorepo with unexpected toolchain vulnerabilities
464
254
 
465
- ```bash
466
- cve-lite /path/to/project --report
467
- cve-lite /path/to/project --report ./my-report --no-open
468
- ```
255
+ [20+ case studies across npm, pnpm, Yarn, and Bun projects ->](https://owasp.org/cve-lite-cli/docs/case-studies)
469
256
 
470
- See the [HTML Report guide](https://owasp.org/cve-lite-cli/docs/html-report) for the full option reference and output details.
257
+ In-repo lockfile fixtures for most projects live under [`examples/`](examples/readme.md) - clone and scan immediately without downloading full upstream checkouts.
471
258
 
472
- ## Offline support
259
+ These are not demos. They are documented scans against real codebases with real findings, recorded before and after applying fix commands.
473
260
 
474
- For teams in enterprise, restricted-network, or air-gapped environments:
261
+ If you maintain an open-source JavaScript or TypeScript project and want CVE Lite CLI evaluated on it, open an issue and share the repository.
475
262
 
476
- ```bash
477
- # Sync advisory data locally
478
- cve-lite advisories sync
263
+ ## Press
479
264
 
480
- # Scan with no runtime API calls
481
- cve-lite . --offline
482
- ```
265
+ - **[Sniff out stale AI override advice with this open source CLI](https://www.theregister.com/security/2026/06/23/sniff-out-stale-ai-override-advice-with-this-open-source-cli/5259853)** - The Register (Thomas Claburn, Senior Reporter), June 2026
266
+ - **[Shift left: How CVE Lite CLI is transforming developer security](https://sdtimes.com/security/shift-left-how-cve-lite-cli-is-transforming-developer-security/)** - SD Times (David Rubinstein, Editor-in-Chief), June 2026
267
+ - **[As AI speeds coding, CVE Lite CLI keeps security deliberately AI-free](https://www.csoonline.com/article/4176701/as-ai-speeds-coding-cve-lite-cli-keeps-security-deliberately-ai-free.html)** - CSO Online (Shweta Sharma), May 2026
268
+ - **[CVE Lite CLI: Open-source dependency vulnerability scanner](https://www.helpnetsecurity.com/2026/05/20/cve-lite-cli-open-source-dependency-vulnerability-scanner/)** - Help Net Security, May 2026
483
269
 
484
- Syncing ~217,065 advisory records runs in under 9 seconds after bulk SQLite ingestion optimizations — roughly **9.9x faster** than the initial implementation.
270
+ [Full press coverage ->](https://owasp.org/cve-lite-cli/docs/press)
485
271
 
486
- See the [Offline Advisory DB guide](https://owasp.org/cve-lite-cli/docs/offline-advisory-db) for the full workflow including CI, scheduled refresh, and controlled-network patterns.
272
+ ## Recognized by OWASP
487
273
 
488
- ## Who uses it
274
+ OWASP (Open Web Application Security Project) is the globally recognized nonprofit behind the security standards followed by millions of developers worldwide - most notably the [OWASP Top 10](https://owasp.org/www-project-top-ten/), the most widely cited web application security reference in the industry. Organizations from startups to Fortune 500 companies use OWASP guidelines as the foundation of their security programs.
489
275
 
490
- CVE Lite CLI is the only free, OWASP-recognized vulnerability scanner purpose-built for JavaScript and TypeScript that combines validated fix commands, parent-aware transitive remediation, and offline scanning in a single lightweight CLI.
276
+ CVE Lite CLI is an [OWASP Lab Project](https://owasp.org/cve-lite-cli) - reviewed and accepted by the OWASP community as a vendor-neutral, open source security tool.
491
277
 
492
- It is a good fit for:
278
+ **Where it fits in the OWASP ecosystem:**
493
279
 
494
- - **Independent developers and OSS maintainers** — quick pre-release check without any platform overhead or cost
495
- - **Startups and small teams** — lightweight CI gate at no cost, with fix commands ready to run immediately
496
- - **Consultants** — scan a client project in seconds and hand over a concrete, copy-and-run remediation plan
497
- - **Enterprise teams with restricted networks** — offline advisory DB removes the need for runtime outbound calls during scans
498
- - **Teams running npm, pnpm, Yarn, and Bun** — unified scanning across all four package managers in one tool
280
+ CVE Lite CLI fills a specific gap - fast, local-first JS/TS dependency scanning close to release time - that broader OWASP tools are not optimized for:
499
281
 
500
- See the [CI and Workflow Integration guide](https://owasp.org/cve-lite-cli/docs/workflow-integration) for concrete patterns across these scenarios.
282
+ | Tool | Focus |
283
+ |---|---|
284
+ | CVE Lite CLI | Lockfile-first, local developer CLI, remediation-focused, JS/TS |
285
+ | OWASP Dependency-Check | Multi-language, SAST-style, broader ecosystem |
286
+ | OWASP dep-scan | Multi-language and environment, SBOM and cloud-native |
287
+ | OWASP Dependency-Track | Platform and SBOM management, not a local CLI |
501
288
 
502
- Using CVE Lite CLI at your company or in your projects? [Share your use case in the community thread](https://github.com/OWASP/cve-lite-cli/discussions/481) - we'd love to hear about it.
289
+ CVE Lite CLI complements these tools. It is not a replacement for continuous monitoring or full SBOM management - it is the fast local check you run before pushing.
503
290
 
504
291
  ## Community and adoption
505
292
 
@@ -507,15 +294,11 @@ CVE Lite CLI is used in production across organizations and independent develope
507
294
 
508
295
  Notable adopters include:
509
296
 
510
- - **Moody's** (via Bitovi) - embedded in the shared CI/CD pipeline serving 600+ UI repositories
511
- - **Discord** - evaluated by the Staff Product Security Engineering team
512
- - **Vertica** - used by developers and SRE teams across projects
513
297
  - **DINUM** (France) - integrated across four French government digital service repositories, including official AI training infrastructure for civil servants
514
298
  - **DGAFP** (France) - Ministry for Civil Service, used as a pre-commit hook on a public-sector HR chatbot
515
299
  - **Government of British Columbia** (Canada) - running as a required merge gate alongside Trivy at the Ministry of Citizens' Services
516
300
  - **Valibot** and **Formish** - integrated as a GitHub Action and dev script with branch protection
517
301
 
518
- For a full view of adoption evidence and press coverage, see [`docs/community/impact.md`](docs/community/impact.md).
519
302
 
520
303
  ## Current limitations
521
304
 
@@ -535,75 +318,24 @@ For a full view of adoption evidence and press coverage, see [`docs/community/im
535
318
 
536
319
  This is intentional. Because CVE Lite CLI is a security-oriented tool, runtime dependencies are kept minimal and reviewable.
537
320
 
538
- ## Roadmap
539
-
540
- See the [Roadmap](https://owasp.org/cve-lite-cli/docs/roadmap) for the full plan. Phases 1 and 2 are complete. Phase 3 (ecosystem coverage: Bun, Deno, parser improvements) is in progress.
541
-
542
- ## Troubleshooting
543
-
544
- See the [Troubleshooting guide](https://owasp.org/cve-lite-cli/docs/troubleshooting) for common issues: no lockfile found, zero results, slow advisory sync, offline DB errors, `--fix` skipping findings, and CI failures.
545
-
546
- ## Parser coverage
547
-
548
- See the [Parser Coverage guide](https://owasp.org/cve-lite-cli/docs/parser-coverage) for supported lockfile formats, selection priority, the `package.json` fallback, and known edge cases including monorepos and private registries.
549
-
550
- See the [Remediation Strategy guide](https://owasp.org/cve-lite-cli/docs/remediation-strategy) for how CVE Lite CLI chooses package upgrade targets and parent update paths.
551
-
552
- ## Website
553
-
554
- The public documentation site is published at [owasp.org/cve-lite-cli](https://owasp.org/cve-lite-cli/) and is built with Docusaurus from [`website/`](website/). All public guides and case studies live under [`website/docs/`](website/docs/) — that folder is the single source of truth for user-facing documentation.
321
+ ## More documentation
555
322
 
556
- ```bash
557
- cd website
558
- npm install
559
- npm run build
560
- ```
561
-
562
- ## Governance
563
-
564
- CVE Lite CLI is an OWASP Lab Project maintained by Sonu Kapoor as project lead. The project follows a single-maintainer (benevolent dictator) governance model. The project lead makes final decisions on scope, design direction, and releases after considering input from contributors and the wider community.
565
-
566
- ### Roles
567
-
568
- - **Project lead** — currently Sonu Kapoor. Owns the roadmap, sets release cadence, reviews and merges pull requests, and acts as the OWASP project leader for the Foundation.
569
- - **Contributors** — anyone who opens an issue, proposes a pull request, or improves the documentation. No prior commit history is required to contribute, and contributions are welcome from outside OWASP.
570
-
571
- ### Decision-making
572
-
573
- - Significant changes (new features, breaking changes, scope decisions) start as a GitHub issue so the design can be discussed in public before code is written.
574
- - Pull requests are reviewed by the project lead. Small fixes can land directly. Larger changes may require revision or follow-up issues.
575
- - Releases are cut by the project lead when accumulated changes warrant a version bump, following the process in [CONTRIBUTING.md](https://github.com/OWASP/cve-lite-cli/blob/main/src/docs/CONTRIBUTING.md).
576
-
577
- ### Dispute resolution
578
-
579
- Technical disagreements are resolved by the project lead after weighing contributor input. Disputes that relate to community standards or [Code of Conduct](https://github.com/OWASP/cve-lite-cli/blob/main/CODE_OF_CONDUCT.md) enforcement can be escalated to the OWASP Foundation, which acts as a backstop for the project's community norms.
580
-
581
- This governance model may evolve as the contributor base grows. Any change to the model will be documented here and announced via the GitHub repository.
323
+ - [Troubleshooting guide](https://owasp.org/cve-lite-cli/docs/troubleshooting) - no lockfile found, zero results, slow advisory sync, offline DB errors, `--fix` skipping findings, CI failures
324
+ - [Parser Coverage guide](https://owasp.org/cve-lite-cli/docs/parser-coverage) - supported lockfile formats, selection priority, `package.json` fallback, monorepos, private registries
325
+ - [Remediation Strategy guide](https://owasp.org/cve-lite-cli/docs/remediation-strategy) - how CVE Lite CLI chooses upgrade targets and parent update paths
582
326
 
583
327
  ## Security and verification
584
328
 
585
- CVE Lite CLI signs both the source code release and the build artifact for each release. Either signature is sufficient on its own.
586
-
587
- **Source code (signed git tags).** Starting with releases after v1.12.1, every release tag is a GPG-signed annotated tag. The project lead's public key is published at [`https://github.com/sonukapoor.gpg`](https://github.com/sonukapoor.gpg). The private key is held only on the project lead's local machine — not on GitHub, not on the npm registry, not in CI. Verify with:
588
-
589
- ```bash
590
- curl -sSL https://github.com/sonukapoor.gpg | gpg --import
591
- git tag -v vX.Y.Z
592
- ```
593
-
594
- **Release tarball (Sigstore Artifact Attestations).** Each GitHub release attaches an `cve-lite-cli-X.Y.Z.tgz` asset signed at build time via [GitHub Artifact Attestations](https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds). The signing keys are ephemeral OIDC-issued keys generated per build, providing SLSA Level 2 equivalent build provenance. Verify with:
329
+ Every release is signed - GPG-signed git tags for source, Sigstore Artifact Attestations for the release tarball, and ECDSA signatures via the npm registry. Verify with:
595
330
 
596
331
  ```bash
597
332
  gh attestation verify cve-lite-cli-X.Y.Z.tgz --repo OWASP/cve-lite-cli
598
- ```
599
-
600
- **npm-installed package.** The npm registry adds an ECDSA signature to every published package, independent of the project's own signing keys above:
601
-
602
- ```bash
603
333
  npm audit signatures
604
334
  ```
605
335
 
606
- For full verification details, fingerprints, and security issue reports, see [SECURITY.md](https://github.com/OWASP/cve-lite-cli/blob/main/src/docs/SECURITY.md). For the project's threat model, trust boundaries, and how common implementation weaknesses are countered, see the [Security Assurance Case](https://owasp.org/cve-lite-cli/docs/security-assurance-case).
336
+ For full details, fingerprints, and the project's threat model, see [SECURITY.md](https://github.com/OWASP/cve-lite-cli/blob/main/src/docs/SECURITY.md) and the [Security Assurance Case](https://owasp.org/cve-lite-cli/docs/security-assurance-case).
337
+
338
+ For governance details - roles, decision-making, and dispute resolution - see [CONTRIBUTING.md](https://github.com/OWASP/cve-lite-cli/blob/main/src/docs/CONTRIBUTING.md).
607
339
 
608
340
  ## Contributing
609
341
 
@@ -627,6 +359,8 @@ For bug reports and feature requests: [GitHub Issues](https://github.com/OWASP/c
627
359
 
628
360
  Helpful feedback includes reproducible bug reports, real-world lockfile edge cases, ideas for clearer output and remediation guidance, and CI or JSON workflow examples.
629
361
 
362
+ Using CVE Lite CLI at your company or in your projects? [Share your use case in the community thread](https://github.com/OWASP/cve-lite-cli/discussions/481).
363
+
630
364
  For security-related reporting: [SECURITY.md](https://github.com/OWASP/cve-lite-cli/blob/main/src/docs/SECURITY.md)
631
365
 
632
366
  This project follows a [Code of Conduct](https://github.com/OWASP/cve-lite-cli/blob/main/CODE_OF_CONDUCT.md). Please review it before participating.
@@ -635,7 +369,7 @@ If CVE Lite CLI helps your release workflow, a [GitHub star](https://github.com/
635
369
 
636
370
  ## Contributors
637
371
 
638
- Thanks to everyone who helps improve CVE Lite CLI — issues, pull requests, documentation, case studies, and real-world lockfile feedback all count.
372
+ Thanks to everyone who helps improve CVE Lite CLI - issues, pull requests, documentation, case studies, and real-world lockfile feedback all count.
639
373
 
640
374
  <p align="center">
641
375
  <a href="https://github.com/OWASP/cve-lite-cli/graphs/contributors">
@@ -655,8 +389,6 @@ New here? See [CONTRIBUTING.md](https://github.com/OWASP/cve-lite-cli/blob/main/
655
389
 
656
390
  ---
657
391
 
658
- *Most tools tell you what's wrong. CVE Lite CLI tells you what to run.*
659
-
660
392
  ## License
661
393
 
662
- MIT — built in public and maintained as an OWASP Foundation Project by Sonu Kapoor.
394
+ MIT - built in public and maintained as an OWASP Foundation Project by Sonu Kapoor.