@adobe/spacecat-shared-http-utils
Shared modules of the Spacecat Services - HTTP Utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adobe org migrated publishing to GitHub Actions CI with SLSA attestation; this is the expected publisher going forward. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes a base64-encoded public key PEM for SPKI import — standard JWT verification pattern, not malicious. | ai |
Versions (showing 100 of 116)
| Version | Deps | Published |
|---|---|---|
| 1.34.0 | 4 / 5 | |
| 1.33.1 | 4 / 5 | |
| 1.33.0 | 4 / 5 | |
| 1.32.0 | 4 / 5 | |
| 1.31.0 | 4 / 5 | |
| 1.30.0 | 4 / 5 | |
| 1.29.1 | 4 / 5 | |
| 1.29.0 | 4 / 5 | |
| 1.28.2 | 4 / 5 | |
| 1.28.1 | 4 / 5 | |
| 1.28.0 | 4 / 5 | |
| 1.27.2 | 4 / 5 | |
| 1.27.1 | 4 / 5 | |
| 1.27.0 | 4 / 5 | |
| 1.26.1 | 4 / 5 | |
| 1.26.0 | 4 / 5 | |
| 1.25.2 | 3 / 4 | |
| 1.25.1 | 3 / 4 | |
| 1.25.0 | 3 / 4 | |
| 1.24.1 | 3 / 4 | |
| 1.24.0 | 3 / 4 | |
| 1.23.0 | 3 / 4 | |
| 1.22.2 | 3 / 4 | |
| 1.22.1 | 3 / 4 | |
| 1.22.0 | 3 / 4 | |
| 1.21.1 | 3 / 4 | |
| 1.21.0 | 3 / 4 | |
| 1.20.1 | 3 / 4 | |
| 1.20.0 | 4 / 4 | |
| 1.19.4 | 4 / 4 | |
| 1.19.3 | 4 / 4 | |
| 1.19.2 | 4 / 4 | |
| 1.19.1 | 4 / 4 | |
| 1.19.0 | 4 / 4 | |
| 1.18.2 | 4 / 4 | |
| 1.18.1 | 4 / 4 | |
| 1.18.0 | 4 / 4 | |
| 1.17.9 | 4 / 4 | |
| 1.17.8 | 4 / 4 | |
| 1.17.7 | 4 / 4 | |
| 1.17.6 | 4 / 4 | |
| 1.17.5 | 4 / 4 | |
| 1.17.4 | 4 / 4 | |
| 1.17.3 | 4 / 4 | |
| 1.17.2 | 4 / 4 | |
| 1.17.1 | 4 / 4 | |
| 1.17.0 | 4 / 4 | |
| 1.16.0 | 4 / 4 | |
| 1.15.2 | 4 / 4 | |
| 1.15.1 | 4 / 4 | |
| 1.15.0 | 4 / 4 | |
| 1.14.4 | 4 / 4 | |
| 1.14.3 | 4 / 4 | |
| 1.14.2 | 4 / 4 | |
| 1.14.1 | 4 / 4 | |
| 1.14.0 | 4 / 4 | |
| 1.13.2 | 4 / 4 | |
| 1.13.1 | 4 / 4 | |
| 1.13.0 | 4 / 4 | |
| 1.12.1 | 4 / 4 | |
| 1.12.0 | 4 / 4 | |
| 1.11.0 | 4 / 4 | |
| 1.10.6 | 4 / 4 | |
| 1.10.5 | 4 / 4 | |
| 1.10.4 | 4 / 4 | |
| 1.10.3 | 4 / 4 | |
| 1.10.2 | 4 / 4 | |
| 1.10.1 | 4 / 4 | |
| 1.10.0 | 4 / 4 | |
| 1.9.12 | 4 / 4 | |
| 1.9.11 | 4 / 4 | |
| 1.9.10 | 4 / 4 | |
| 1.9.9 | 4 / 4 | |
| 1.9.8 | 4 / 4 | |
| 1.9.7 | 4 / 4 | |
| 1.9.6 | 4 / 4 | |
| 1.9.5 | 4 / 4 | |
| 1.9.4 | 4 / 4 | |
| 1.9.3 | 4 / 4 | |
| 1.9.2 | 4 / 4 | |
| 1.9.1 | 4 / 4 | |
| 1.9.0 | 4 / 4 | |
| 1.8.0 | 4 / 4 | |
| 1.7.3 | 4 / 4 | |
| 1.7.2 | 4 / 4 | |
| 1.7.1 | 4 / 4 | |
| 1.7.0 | 4 / 4 | |
| 1.6.18 | 4 / 4 | |
| 1.6.17 | 4 / 4 | |
| 1.6.16 | 4 / 4 | |
| 1.6.15 | 4 / 4 | |
| 1.6.14 | 4 / 4 | |
| 1.6.13 | 4 / 4 | |
| 1.6.12 | 4 / 4 | |
| 1.6.11 | 4 / 4 | |
| 1.6.10 | 4 / 4 | |
| 1.6.9 | 4 / 4 | |
| 1.6.8 | 4 / 4 | |
| 1.6.7 | 4 / 4 | |
| 1.6.6 | 4 / 4 |
v1.34.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.33.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.