@sap-cloud-sdk/resilience
SAP Cloud SDK for JavaScript resilience
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): SAP Cloud SDK publishes via GitHub Actions; gitHead absence is a CI config change, not a threat signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source program office account; routine org-level maintainer rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer alongside addition of SAP org account is normal team rotation. | ai | |
| dependencies | unvetted-dep:opossum | AI (dependencies): opossum is a well-known, legitimate Node.js circuit breaker library; its use is expected and appropriate for a resilience-focused package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency in package.json; phantom-dep flag is a false positive for this package where axios is used indirectly or in config files. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.8.0 | 4 / 6 | |
| 4.7.0 | 4 / 6 | |
| 4.6.0 | 4 / 4 | |
| 4.5.1 | 4 / 4 | |
| 4.5.0 | 4 / 4 | |
| 4.4.0 | 4 / 4 | |
| 4.3.1 | 4 / 4 | |
| 4.3.0 | 4 / 4 | |
| 4.2.0 | 4 / 4 | |
| 4.1.2 | 4 / 4 | |
| 4.1.1 | 4 / 4 | |
| 4.1.0 | 4 / 4 | |
| 4.0.2 | 4 / 4 | |
| 4.0.1 | 4 / 4 | |
| 4.0.0 | 4 / 4 |
v4.8.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
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.