@sap-cloud-sdk/odata-common
SAP Cloud SDK for JavaScript common functions of OData client generator and OpenAPI clint generator.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): SAP org-level admin account rotation; consistent with large org package management practices. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer in favor of org admin account; expected for SAP's package governance. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a minor metadata gap, not a supply chain risk. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/util | AI (dependencies): Sibling SAP Cloud SDK package published from the same official SAP/cloud-sdk-js repo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:voca | AI (dependencies): voca is a well-known, stable string manipulation library (v1.4.1+); no known malicious history. Legitimate dependency for OData string handling. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/http-client | AI (dependencies): Sibling SAP Cloud SDK package published from the same official SAP/cloud-sdk-js repo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/connectivity | AI (dependencies): Sibling SAP Cloud SDK package published from the same official SAP/cloud-sdk-js repo; unvetted status is a pipeline artifact, not a security concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 6 / 5 | |
| 4.6.0 | 6 / 2 | |
| 4.5.1 | 6 / 2 | |
| 4.5.0 | 6 / 2 | |
| 4.4.0 | 6 / 2 | |
| 4.3.1 | 6 / 2 | |
| 4.3.0 | 6 / 2 | |
| 4.2.0 | 7 / 2 | |
| 4.1.2 | 7 / 2 | |
| 4.1.1 | 7 / 2 | |
| 4.1.0 | 7 / 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. 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.