@sap-cloud-sdk/openapi-generator
SAP Cloud SDK for JavaScript OpenAPI client 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:swagger2openapi | AI (dependencies): swagger2openapi is a well-known OpenAPI conversion utility; its use in an OpenAPI generator tool is entirely appropriate and expected. | ai | |
| phantom-deps | phantom-dep:@sap-cloud-sdk/openapi | AI (phantom-deps): Explicitly acknowledged false positive — package.json scripts use --ignores='@sap-cloud-sdk/openapi' in depcheck. It's a sibling package in the same monorepo used as a type/runtime dep. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 8 / 9 | |
| 4.6.0 | 8 / 6 | |
| 4.5.1 | 8 / 6 | |
| 4.5.0 | 8 / 6 | |
| 4.4.0 | 7 / 5 | |
| 4.3.1 | 7 / 5 | |
| 4.3.0 | 7 / 5 | |
| 4.2.0 | 7 / 5 | |
| 4.1.2 | 7 / 5 | |
| 4.1.1 | 7 / 5 | |
| 4.1.0 | 7 / 5 | |
| 4.0.2 | 7 / 4 | |
| 4.0.1 | 7 / 4 | |
| 4.0.0 | 7 / 4 |
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-18, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marikaner) than the most recent previously approved version (deekshas8) on 2025-03-05, but marikaner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.