cve-lite-cli 1.0.0 → 1.0.2
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 +100 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# CVE Lite CLI
|
|
2
2
|
|
|
3
|
-
Fast
|
|
3
|
+
A **Free**, **Fast** and **developer-friendly** vulnerability scanning for JavaScript and TypeScript projects.
|
|
4
4
|
|
|
5
5
|
**CVE Lite CLI** helps developers scan their projects for known package vulnerabilities without signing up for an expensive platform. It is built for the moment right before release, when you want a clear answer, a practical fix plan, and a tool you can actually afford to use.
|
|
6
6
|
|
|
@@ -8,8 +8,8 @@ Fast, developer-friendly vulnerability scanning for JavaScript and TypeScript pr
|
|
|
8
8
|
|
|
9
9
|
Below is a real example of the console experience. In a terminal, the severity labels, summaries, and section headers are colorized for readability.
|
|
10
10
|
|
|
11
|
-

|
|
12
|
-

|
|
11
|
+

|
|
12
|
+

|
|
13
13
|
|
|
14
14
|
That is the core idea: install it, point it at your project, and immediately get a practical fix plan instead of a wall of raw advisories.
|
|
15
15
|
|
|
@@ -116,9 +116,23 @@ At the end of each run, CVE Lite CLI prints a short final status line so users i
|
|
|
116
116
|
|
|
117
117
|
### 11. Small runtime footprint
|
|
118
118
|
|
|
119
|
-
|
|
120
119
|
This project intentionally keeps runtime dependencies minimal to reduce attack surface and keep the tool easier to review.
|
|
121
120
|
|
|
121
|
+
## Dependency footprint
|
|
122
|
+
|
|
123
|
+
CVE Lite CLI is intentionally designed with a very small dependency surface.
|
|
124
|
+
|
|
125
|
+
**Runtime dependencies**
|
|
126
|
+
- `yaml`
|
|
127
|
+
- `yarn-lockfile`
|
|
128
|
+
|
|
129
|
+
**Development dependencies**
|
|
130
|
+
- `@types/node`
|
|
131
|
+
- `tsx`
|
|
132
|
+
- `typescript`
|
|
133
|
+
|
|
134
|
+
This is a deliberate design choice. Because CVE Lite CLI is itself a security-oriented tool, we want to minimize unnecessary third-party packages and keep the runtime as small and reviewable as possible.
|
|
135
|
+
|
|
122
136
|
## Example use cases
|
|
123
137
|
|
|
124
138
|
CVE Lite CLI is a good fit for:
|
|
@@ -216,6 +230,88 @@ Use JSON output for custom reporting:
|
|
|
216
230
|
cve-lite . --json > cve-lite-report.json
|
|
217
231
|
```
|
|
218
232
|
|
|
233
|
+
## Comparison with other tools
|
|
234
|
+
|
|
235
|
+
CVE Lite CLI is not trying to be everything for everyone. It is designed to be one of the easiest and most actionable vulnerability scanners for JavaScript and TypeScript developers who want fast release-time checks without the cost and complexity of a full security platform.
|
|
236
|
+
|
|
237
|
+
### Where CVE Lite CLI stands out
|
|
238
|
+
|
|
239
|
+
Compared with other tools in this space, CVE Lite CLI focuses on:
|
|
240
|
+
|
|
241
|
+
- **free to use**
|
|
242
|
+
- **fast to run**
|
|
243
|
+
- **easy to understand**
|
|
244
|
+
- **practical remediation guidance** instead of just raw advisory dumps
|
|
245
|
+
- **clear direct vs transitive visibility**
|
|
246
|
+
- **top priority fixes** and a suggested fix plan
|
|
247
|
+
- support for **npm**, **pnpm**, and **Yarn** lockfiles
|
|
248
|
+
- **SARIF** and **JSON** output for CI and automation
|
|
249
|
+
- a **lightweight**, **security-conscious** dependency footprint
|
|
250
|
+
- a **developer-friendly** option for teams that want useful **CVE scanning without paying for a larger commercial product**
|
|
251
|
+
|
|
252
|
+
### At a glance
|
|
253
|
+
|
|
254
|
+
| Tool | Best at | Ecosystem scope | Lockfile support | Guided remediation | JSON/SARIF | Best fit |
|
|
255
|
+
|---|---|---|---|---|---|---|
|
|
256
|
+
| **CVE Lite CLI** | Fast, developer-friendly pre-release CVE scanning | Focused on JS/TS | npm, pnpm, Yarn | **Yes** | **Yes** | Developers and small teams who want a free, practical release-time check |
|
|
257
|
+
| `npm audit` | Built-in npm auditing | npm-centric | npm | Basic remediation info | Limited compared to dedicated scanner workflows | Teams already living fully inside npm |
|
|
258
|
+
| OSV-Scanner | Broad multi-ecosystem scanning | Broad | Many ecosystems and lockfiles | More general-purpose | Strong machine-readable workflows | Teams needing wider ecosystem coverage |
|
|
259
|
+
| Snyk CLI | Broader enterprise security workflows | Broad | Strong ecosystem coverage | Strong commercial guidance | Strong | Teams adopting a larger security platform |
|
|
260
|
+
| Socket CLI | Broader package and supply-chain risk visibility | Broad | Multi-ecosystem/package-risk focus | Strong for package risk workflows | Strong | Teams that want more than CVE scanning alone |
|
|
261
|
+
|
|
262
|
+
|
|
263
|
+
### CVE Lite CLI vs npm audit
|
|
264
|
+
|
|
265
|
+
`npm audit` is the built-in default for npm users, which makes it convenient when your workflow is entirely npm-based.
|
|
266
|
+
|
|
267
|
+
CVE Lite CLI stands out when you want:
|
|
268
|
+
|
|
269
|
+
- support across npm, pnpm, and Yarn lockfiles
|
|
270
|
+
- cleaner, more guided console output
|
|
271
|
+
- priority fixes and a suggested remediation plan
|
|
272
|
+
- a more focused pre-release scanning experience for JS/TS teams
|
|
273
|
+
|
|
274
|
+
### CVE Lite CLI vs OSV-Scanner
|
|
275
|
+
|
|
276
|
+
OSV-Scanner supports many ecosystems and lockfile types, which makes it broader overall.
|
|
277
|
+
|
|
278
|
+
CVE Lite CLI stands out when you want:
|
|
279
|
+
|
|
280
|
+
- a narrower, easier-to-understand tool built specifically around JS/TS dependency workflows
|
|
281
|
+
- remediation-first output instead of a more general multi-ecosystem scanner experience
|
|
282
|
+
- a more approachable local workflow for everyday developers
|
|
283
|
+
|
|
284
|
+
### CVE Lite CLI vs Snyk CLI
|
|
285
|
+
|
|
286
|
+
Snyk CLI is part of a much broader commercial platform with wider enterprise coverage.
|
|
287
|
+
|
|
288
|
+
CVE Lite CLI stands out when you want:
|
|
289
|
+
|
|
290
|
+
- a simpler and lighter dependency CVE workflow
|
|
291
|
+
- an affordable option for small teams, startups, consultants, and independent developers
|
|
292
|
+
- a focused tool for lockfile-based release checks without adopting a larger platform
|
|
293
|
+
|
|
294
|
+
### CVE Lite CLI vs Socket CLI
|
|
295
|
+
|
|
296
|
+
Socket CLI goes beyond CVEs into broader package and supply-chain risk signals.
|
|
297
|
+
|
|
298
|
+
CVE Lite CLI stands out when you want:
|
|
299
|
+
|
|
300
|
+
- a focused dependency vulnerability scanner
|
|
301
|
+
- a straightforward answer to “what should I fix before release?”
|
|
302
|
+
- readable output centered on known vulnerability findings and practical next steps
|
|
303
|
+
|
|
304
|
+
### Best fit
|
|
305
|
+
|
|
306
|
+
CVE Lite CLI is best for:
|
|
307
|
+
|
|
308
|
+
- developers shipping JavaScript or TypeScript applications
|
|
309
|
+
- teams that want a lightweight release gate
|
|
310
|
+
- maintainers who want actionable vulnerability output without heavy platform overhead
|
|
311
|
+
- users who care about simplicity, readability, and fast adoption
|
|
312
|
+
|
|
313
|
+
If your goal is a practical developer-first CVE scan right before release, CVE Lite CLI is designed to be one of the most approachable options in that workflow.
|
|
314
|
+
|
|
219
315
|
## Philosophy
|
|
220
316
|
|
|
221
317
|
CVE Lite CLI is not trying to be everything.
|