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
Copy file name to clipboardExpand all lines: docs/lib/content/commands/npm-audit.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,16 @@ The `audit signatures` command will also verify the provenance attestations of d
42
42
Because provenance attestations are such a new feature, security features may be added to (or changed in) the attestation format over time.
43
43
To ensure that you're always able to verify attestation signatures check that you're running the latest version of the npm CLI. Please note this often means updating npm beyond the version that ships with Node.js.
44
44
45
+
To include the full sigstore attestation bundles in JSON output, use:
// Currently we only care about missing signatures on registries that provide a public key
332
341
// We could make this configurable in the future with a strict/paranoid mode
@@ -346,6 +355,16 @@ class VerifySignatures {
346
355
// Track verified attestations separately to registry signatures, as all packages on registries with signing keys are expected to have registry signatures, but not all packages have provenance and publish attestations.
0 commit comments