gadriel 1.3.0 → 1.4.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 +25 -0
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -198,6 +198,31 @@ Full onboarding guide: [https://gadriel.ai/docs](https://gadriel.ai/docs)
|
|
|
198
198
|
|
|
199
199
|
Output formats: `--format table|json|html|ocsf`.
|
|
200
200
|
|
|
201
|
+
A global `--json` works on every command that has a machine-readable mode
|
|
202
|
+
(`findings`, `verdict`, `skills list`, `store list`, `store status`,
|
|
203
|
+
`learn status`, `doctor`, `policies`, `config scoring`) and overrides that
|
|
204
|
+
command's own `--format`, so CI can pipe any of them without knowing which
|
|
205
|
+
flag each one takes:
|
|
206
|
+
|
|
207
|
+
```bash
|
|
208
|
+
gadriel findings --json | jq '.findings[] | select(.severity == "high")'
|
|
209
|
+
gadriel verdict --json | jq -r '.verdict'
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
`--quiet` is a separate mode and does not imply JSON. `gadriel sbom --format`
|
|
213
|
+
is unaffected — there `--format` selects the SBOM *standard* (SPDX vs
|
|
214
|
+
CycloneDX), not the encoding.
|
|
215
|
+
|
|
216
|
+
### Re-running `init`
|
|
217
|
+
|
|
218
|
+
`init` refuses to overwrite an initialised repo unless you say how:
|
|
219
|
+
|
|
220
|
+
| Flag | Effect |
|
|
221
|
+
|------|--------|
|
|
222
|
+
| `--upgrade` | Merge new settings and templates. **Scan data is preserved** — `findings.json`, `pillar-scores.json` and `metrics/` are left alone. |
|
|
223
|
+
| `--add-missing` | Only add files that are absent; touch nothing that exists. |
|
|
224
|
+
| `--force` | Overwrite everything, **including scan results**. Use after a partial or corrupted install. |
|
|
225
|
+
|
|
201
226
|
> The older `gadriel code <verb>` spelling (e.g. `gadriel code scan`) still
|
|
202
227
|
> works as a hidden alias, so existing hooks and CI pipelines keep running,
|
|
203
228
|
> but the top-level verbs above are the current form.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "gadriel",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.4.0",
|
|
4
4
|
"description": "Gadriel - Code-security CLI for AI-assisted development",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"security",
|
|
@@ -34,10 +34,10 @@
|
|
|
34
34
|
"node": ">=18"
|
|
35
35
|
},
|
|
36
36
|
"optionalDependencies": {
|
|
37
|
-
"@gadriel/cli-linux-x64": "1.
|
|
38
|
-
"@gadriel/cli-linux-arm64": "1.
|
|
39
|
-
"@gadriel/cli-darwin-x64": "1.
|
|
40
|
-
"@gadriel/cli-darwin-arm64": "1.
|
|
41
|
-
"@gadriel/cli-win32-x64": "1.
|
|
37
|
+
"@gadriel/cli-linux-x64": "1.4.0",
|
|
38
|
+
"@gadriel/cli-linux-arm64": "1.4.0",
|
|
39
|
+
"@gadriel/cli-darwin-x64": "1.4.0",
|
|
40
|
+
"@gadriel/cli-darwin-arm64": "1.4.0",
|
|
41
|
+
"@gadriel/cli-win32-x64": "1.4.0"
|
|
42
42
|
}
|
|
43
43
|
}
|