@sap-cloud-sdk/odata-v4
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a cosmetic regression, 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; consistent with org-level maintainer management for this SAP package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer alongside addition of org admin account is a normal SAP org rotation pattern. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/util | AI (dependencies): Sibling package from the same SAP Cloud SDK monorepo, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/odata-common | AI (dependencies): Sibling package from the same SAP Cloud SDK monorepo, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/http-client | AI (dependencies): Sibling package from the same SAP Cloud SDK monorepo, released in lockstep. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/connectivity | AI (dependencies): Sibling package from the same SAP Cloud SDK monorepo, released in lockstep. Not a third-party risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 6 / 5 | |
| 4.6.0 | 6 / 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 | 7 / 3 | |
| 4.1.2 | 7 / 3 | |
| 4.1.1 | 7 / 3 | |
| 4.1.0 | 7 / 3 |
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. 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.