@sap-cloud-sdk/openapi
SAP Cloud SDK for JavaScript openapi
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 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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.