@corgea/cli 1.9.0 → 1.9.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 +36 -0
- package/package.json +1 -1
- package/vendor/aarch64-apple-darwin/corgea/corgea +0 -0
- package/vendor/aarch64-unknown-linux-gnu/corgea/corgea +0 -0
- package/vendor/x86_64-apple-darwin/corgea/corgea +0 -0
- package/vendor/x86_64-pc-windows-msvc/corgea/corgea.exe +0 -0
- package/vendor/x86_64-unknown-linux-musl/corgea/corgea +0 -0
package/README.md
CHANGED
|
@@ -50,6 +50,42 @@ corgea deps policy init --exist-ok # write starter policy, or keep existing
|
|
|
50
50
|
|
|
51
51
|
See [Dependency Scanning (CLI)](https://docs.corgea.app/cli/deps) for the full flag and exit-code reference.
|
|
52
52
|
|
|
53
|
+
## Install Gate
|
|
54
|
+
|
|
55
|
+
Prefix a package-manager install with `corgea` to vet every package it would
|
|
56
|
+
install — named **and transitive** — against Corgea's vulnerability API *before*
|
|
57
|
+
anything lands on disk. Known-vulnerable or malicious versions block the install;
|
|
58
|
+
a clean set runs the underlying command untouched. Works with `pip`, `npm`,
|
|
59
|
+
`yarn`, `pnpm`, and `uv`.
|
|
60
|
+
|
|
61
|
+
No token required — baseline public CVE checks run out of the box. Try it:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
corgea npm install lodash@4.17.20 # blocks: known-vulnerable (CVE-2025-13465), exits 1
|
|
65
|
+
corgea pip install requests # resolves, checks the verdict, then runs pip
|
|
66
|
+
corgea npm install axios@^1.0.0 # ranges resolve to a concrete version first
|
|
67
|
+
corgea pip --force install <pkg> # print findings but install anyway
|
|
68
|
+
corgea pip list # non-install subcommands pass straight through
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
`corgea pip install` and `corgea npm install` resolve the **full would-install
|
|
72
|
+
set** (named + transitive) via a safe dry-run, so a vulnerable *transitive*
|
|
73
|
+
dependency blocks too. Blocked findings steer to the fix: each advisory shows
|
|
74
|
+
`fixed in <version>`, and the gate prints the safe version to install instead.
|
|
75
|
+
|
|
76
|
+
The gate also blocks **freshly published** packages — anything published within
|
|
77
|
+
the recency window (default 14 days) — to catch just-shipped typosquats and
|
|
78
|
+
hijacks before advisory feeds catch up. It is on by default; turn it off with
|
|
79
|
+
`recency_gate = false` in `~/.corgea/config.toml`, retune the window with
|
|
80
|
+
`recency_threshold_days`, or pass `--force` for a one-off install.
|
|
81
|
+
|
|
82
|
+
Logging in (`corgea login`) upgrades the gate to authenticated enforcement —
|
|
83
|
+
unverifiable packages, resolution errors, and lookup failures then fail closed
|
|
84
|
+
(public mode warns and continues). Wrapper flags (`--force`, `--json`) go between
|
|
85
|
+
the manager and its command: `corgea npm --force install <pkg>`.
|
|
86
|
+
|
|
87
|
+
See [the CLI docs](https://docs.corgea.app/cli) for the full flag and exit-code reference.
|
|
88
|
+
|
|
53
89
|
## Development Setup
|
|
54
90
|
|
|
55
91
|
### Prerequisites
|
package/package.json
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|