@salutejs/sdds-scan
Salute Design System / React UI kit for SDDS SCAN web applications
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package with 1808 versions; lack of provenance is consistent across the entire salutejs ecosystem. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.356.0 | 2 / 32 | |
| 0.354.0 | 2 / 32 | |
| 0.353.0 | 2 / 32 | |
| 0.351.0 | 2 / 32 | |
| 0.349.1 | 2 / 32 | |
| 0.349.0 | 2 / 32 | |
| 0.347.0 | 2 / 32 | |
| 0.346.0 | 2 / 32 | |
| 0.345.0 | 2 / 32 | |
| 0.344.0 | 2 / 32 | |
| 0.343.0 | 2 / 32 | |
| 0.328.0 | 2 / 41 | |
| 0.326.0 | 2 / 41 |
v0.356.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.354.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.328.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.326.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.