@sap-cloud-sdk/test-util
SAP Cloud SDK for JavaScript test utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor env change, not a supply chain risk for this established SAP package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is an SAP org-level admin account; addition is consistent with SAP's org governance, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual contributor alongside org-admin addition is routine SAP team rotation for this long-lived package. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/util | AI (dependencies): Sibling package within the SAP Cloud SDK monorepo; expected internal dependency, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/connectivity | AI (dependencies): Sibling package within the SAP Cloud SDK monorepo; expected internal dependency, not a third-party risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 2 / 6 | |
| 4.6.0 | 2 / 2 | |
| 4.5.1 | 2 / 2 | |
| 4.5.0 | 2 / 2 | |
| 4.4.0 | 2 / 2 | |
| 4.3.1 | 2 / 2 | |
| 4.3.0 | 2 / 2 | |
| 4.2.0 | 2 / 2 | |
| 4.1.2 | 2 / 2 | |
| 4.1.1 | 2 / 2 | |
| 4.1.0 | 2 / 2 |
v4.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.