← Home

@sap-cloud-sdk/test-util

npm Repository Homepage

SAP Cloud SDK for JavaScript test utilities

15
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jjtangmarikanerkavithasivadavidkna-sapsap-ospo-admin

Keywords

sap-cloud-sdkcloud-sdksap-cloud-platformtest-util

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 15 of 15)

Version Deps Published
4.8.0 2 / 6
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
4.0.2 2 / 2
4.0.1 2 / 2
4.0.0 2 / 2

v4.8.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This 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.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.