@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 16 of 116)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 4 / 4 | |
| 1.6.4 | 4 / 4 | |
| 1.6.3 | 4 / 4 | |
| 1.6.2 | 4 / 4 | |
| 1.6.1 | 4 / 4 | |
| 1.6.0 | 4 / 4 | |
| 1.5.0 | 4 / 4 | |
| 1.4.0 | 3 / 4 | |
| 1.3.5 | 1 / 1 | |
| 1.3.4 | 1 / 1 | |
| 1.3.3 | 1 / 1 | |
| 1.3.2 | 1 / 1 | |
| 1.3.1 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.1 | 1 / 1 | |
| 1.2.0 | 1 / 1 |
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.