@sap-cloud-sdk/util
SAP Cloud SDK for JavaScript general 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): SLSA provenance present; gitHead absence is a metadata quirk, not a security concern for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source program office; routine org-level maintainer rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual in favor of org admin account; normal SAP maintainer rotation. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): False positive: @sap-cloud-sdk/util is a scoped SAP Cloud SDK utility package with 2255 days of history. No resemblance to uuid in purpose, scope, or maintainer. | ai | |
| dependencies | unvetted-dep:voca | AI (dependencies): voca is a well-known, stable string manipulation library. Its use in a utility package is expected and benign. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 5 / 7 | |
| 4.6.0 | 5 / 3 | |
| 4.5.1 | 6 / 3 | |
| 4.5.0 | 6 / 3 | |
| 4.4.0 | 6 / 3 | |
| 4.3.1 | 6 / 3 | |
| 4.3.0 | 6 / 3 | |
| 4.2.0 | 6 / 3 | |
| 4.1.2 | 6 / 3 | |
| 4.1.1 | 6 / 3 | |
| 4.1.0 | 6 / 3 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.