← Home

@sap-cloud-sdk/openapi

SAP Cloud SDK for JavaScript openapi

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-platformopen-api

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is a minor metadata gap, not a supply chain risk for this package. ai
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; org-level rotation expected for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of deekshas8 paired with sap-ospo-admin addition is consistent with SAP internal admin rotation. ai
dependencies unvetted-dep:@sap-cloud-sdk/connectivity AI (dependencies): Sibling package within the SAP Cloud SDK monorepo (SAP/cloud-sdk-js), published at matching version. Expected internal dependency, not a third-party risk. ai
dependencies unvetted-dep:@sap-cloud-sdk/util AI (dependencies): Sibling package within the SAP Cloud SDK monorepo (SAP/cloud-sdk-js), published at matching version. Expected internal dependency, not a third-party risk. ai
phantom-deps phantom-dep:@sap-cloud-sdk/resilience AI (phantom-deps): Same-org sibling dep declared but not directly imported; common in monorepo packages with indirect/transitive usage. Not a security concern. ai
dependencies unvetted-dep:@sap-cloud-sdk/resilience AI (dependencies): Sibling package within the SAP Cloud SDK monorepo (SAP/cloud-sdk-js), published at matching version. Expected internal dependency, not a third-party risk. ai
dependencies unvetted-dep:@sap-cloud-sdk/http-client AI (dependencies): Sibling package within the SAP Cloud SDK monorepo (SAP/cloud-sdk-js), published at matching version. Expected internal dependency, not a third-party risk. ai

Versions (showing 15 of 15)

Version Deps Published
4.8.0 5 / 5
4.7.0 5 / 5
4.6.0 5 / 2
4.5.1 5 / 2
4.5.0 5 / 2
4.4.0 5 / 2
4.3.1 5 / 2
4.3.0 5 / 2
4.2.0 5 / 2
4.1.2 5 / 2
4.1.1 5 / 2
4.1.0 5 / 2
4.0.2 5 / 2
4.0.1 5 / 2
4.0.0 5 / 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

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.