@salutejs/sdds-platform-ai
Salute Design System / React UI kit for SDDS PLATFORM-AI 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 — the axios compromise (March 2026) relied on exactly this gap.
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 Salute org package; provenance absence is consistent across all their releases. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.350.1 | 2 / 32 | |
| 0.350.0 | 2 / 32 | |
| 0.348.0 | 2 / 33 | |
| 0.347.0 | 2 / 33 | |
| 0.346.0 | 2 / 33 | |
| 0.345.0 | 2 / 33 | |
| 0.344.0 | 2 / 33 |
v0.350.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.350.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.348.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.346.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.345.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.344.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.