@sap/swa-for-sapbas-vsx
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sap/bas-sdk | AI (dependencies): First-party SAP dependency consistent with this SAP package's purpose; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-established SAP package; lack of Sigstore provenance is consistent across all 30 versions and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 3 / 20 | |
| 2.0.16 | 3 / 20 | |
| 2.0.15 | 3 / 20 | |
| 2.0.13 | 3 / 20 | |
| 2.0.11 | 3 / 20 | |
| 2.0.10 | 3 / 19 | |
| 2.0.9 | 3 / 19 | |
| 2.0.7 | 3 / 19 | |
| 2.0.6 | 3 / 19 |
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.