@saltcorn/sbadmin2
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package; provenance absence is consistent across all prior versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 2 / 1 | |
| 1.6.0 | 2 / 1 | |
| 1.5.8 | 2 / 1 | |
| 1.5.7 | 2 / 1 | |
| 1.5.6 | 2 / 1 | |
| 1.5.5 | 2 / 1 | |
| 1.5.4 | 2 / 1 | |
| 1.5.3 | 2 / 1 | |
| 1.5.2 | 2 / 1 | |
| 1.5.0 | 2 / 1 | |
| 1.4.6 | 2 / 1 | |
| 1.4.5 | 2 / 1 | |
| 1.4.4 | 2 / 1 | |
| 1.4.3 | 2 / 1 | |
| 1.4.2 | 2 / 1 | |
| 1.4.1 | 2 / 1 |
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.