@sap-cloud-sdk/connectivity
SAP Cloud SDK for JavaScript connectivity
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 present; gitHead absence is a metadata gap, not a security concern for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source program office account; expected org-level rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal SAP maintainer rotation; package remains under SAP org control. | ai | |
| dependencies | unvetted-dep:@sap/xssec | AI (dependencies): Official SAP security client library; expected dependency for SAP Cloud SDK authentication/connectivity. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/util | AI (dependencies): First-party SAP Cloud SDK sibling package; expected dependency for this SDK family. | ai | |
| dependencies | unvetted-dep:jks-js | AI (dependencies): jks-js is a well-known library for parsing Java KeyStore files; appropriate for SAP connectivity which interacts with Java-based SAP systems. | ai | |
| dependencies | unvetted-dep:@sap-cloud-sdk/resilience | AI (dependencies): First-party SAP Cloud SDK sibling package; expected dependency for this SDK family. | ai | |
| dependencies | unvetted-dep:@sap/xsenv | AI (dependencies): Official SAP package for reading environment variables/services; expected in SAP Cloud SDK connectivity. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 9 / 7 | |
| 4.6.0 | 8 / 3 | |
| 4.5.1 | 8 / 3 | |
| 4.5.0 | 8 / 3 | |
| 4.4.0 | 8 / 3 | |
| 4.3.1 | 8 / 3 | |
| 4.3.0 | 8 / 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. 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.