You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 22, 2026. It is now read-only.
git pkgs vulns blame # who introduced each vulnerability
48
50
```
49
51
50
52
## Commands
@@ -261,15 +263,40 @@ Shows dependencies sorted by how long since they were last changed in your repo.
261
263
262
264
### Vulnerability scanning
263
265
266
+
Scan dependencies for known CVEs using the [OSV database](https://osv.dev). Because git-pkgs tracks the full history of every dependency change, it provides context that static scanners can't: who introduced a vulnerability, when it was fixed, and how long you were exposed.
267
+
264
268
```bash
265
-
git pkgs vulns # scan current dependencies for known CVEs
269
+
git pkgs vulns # scan current dependencies
270
+
git pkgs vulns v1.0.0 # scan at a tag, branch, or commit
266
271
git pkgs vulns -s high # only critical and high severity
Uses the [OSV database](https://osv.dev) to check your dependencies against known security advisories. Because git-pkgs tracks the full history, it can show who introduced and fixed each vulnerability. See [docs/vulns.md](docs/vulns.md) for full documentation.
299
+
Vulnerability data is cached locally and refreshed automatically when stale (>24h). Use `gitpkgs vulns sync --refresh` to force an update. See [docs/vulns.md](docs/vulns.md) for full documentation.
0 commit comments