← Home

@sap-cloud-sdk/util

npm Repository Homepage

SAP Cloud SDK for JavaScript general 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-platformutil

Accepted risks

Findings the reviewer chose to accept rather than block on.

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

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

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: deekshas8 → marikaner (on 2025-03-18, known maintainer) provenance

This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-18, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: deekshas8 → marikaner (on 2025-03-05, known maintainer) provenance

This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-05, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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.