@sap-cloud-sdk/generator-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 rotation; consistent with enterprise OSS governance, not a takeover signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of the same org-level maintainer rotation; no malicious signal. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor CI config change, not a supply chain risk. | ai | |
| dependencies | unvetted-dep:voca | AI (dependencies): voca is a legitimate string manipulation library; stable dependency for this SAP Cloud SDK generator package. | ai | |
| dependencies | unvetted-dep:fast-levenshtein | AI (dependencies): fast-levenshtein is a well-known string distance library; stable dependency for this SAP Cloud SDK generator package. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/util | AI (dependencies): Sibling package within the same SAP Cloud SDK monorepo (SAP/cloud-sdk-js); not a third-party risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 7 / 6 | |
| 4.6.0 | 8 / 2 | |
| 4.5.1 | 8 / 2 | |
| 4.5.0 | 8 / 2 | |
| 4.4.0 | 8 / 2 | |
| 4.3.1 | 8 / 2 | |
| 4.3.0 | 8 / 2 | |
| 4.2.0 | 8 / 2 | |
| 4.1.2 | 8 / 2 | |
| 4.1.1 | 8 / 2 | |
| 4.1.0 | 8 / 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.