@salutejs/sdds-serv
Salute Design System / React UI kit for SDDS SERV 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): Salute Design System consistently publishes without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.357.0 | 2 / 35 | |
| 0.355.0 | 2 / 35 | |
| 0.354.0 | 2 / 35 | |
| 0.352.0 | 2 / 35 | |
| 0.350.1 | 2 / 35 | |
| 0.350.0 | 2 / 35 | |
| 0.348.0 | 2 / 36 | |
| 0.347.0 | 2 / 36 | |
| 0.346.0 | 2 / 36 | |
| 0.345.0 | 2 / 36 | |
| 0.344.0 | 2 / 36 | |
| 0.56.0 | 2 / 35 | |
| 0.55.0 | 2 / 35 | |
| 0.47.0 | 2 / 35 | |
| 0.24.0 | 2 / 35 | |
| 0.16.1 | 2 / 35 | |
| 0.16.0 | 2 / 35 |
v0.357.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.355.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.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.47.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.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.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.
v0.16.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.