@sap-cloud-sdk/odata-v2
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 admin rotation (sap-ospo-admin); consistent with internal governance change for a large SAP SDK. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer alongside org admin addition is consistent with SAP internal handoff, not a takeover. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor metadata gap, not a supply chain risk for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): SAP Cloud SDK publishes with SLSA provenance via GitHub Actions CI/CD; this is a stable, expected signal for this package family. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 6 / 6 | |
| 4.6.0 | 6 / 4 | |
| 4.5.1 | 6 / 4 | |
| 4.5.0 | 6 / 4 | |
| 4.4.0 | 6 / 4 | |
| 4.3.1 | 6 / 4 | |
| 4.3.0 | 6 / 4 | |
| 4.2.0 | 7 / 4 | |
| 4.1.2 | 7 / 4 | |
| 4.1.1 | 7 / 4 | |
| 4.1.0 | 7 / 4 |
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.