@salutejs/plasma-b2c
Salute Design System / React UI kit for business-related 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@salutejs/plasma-tokens-b2c | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@salutejs/plasma-tokens-web | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@salutejs/plasma-typo | AI (phantom-deps): Same-org sibling dep; declared but re-exported transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@salutejs/plasma-tokens-web | AI (phantom-deps): Same-org sibling dep; declared but re-exported transitively, stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.619.1 | 7 / 32 | |
| 1.619.0 | 7 / 32 | |
| 1.617.0 | 7 / 33 | |
| 1.616.0 | 7 / 33 | |
| 1.615.0 | 7 / 33 | |
| 1.614.0 | 7 / 33 | |
| 1.613.0 | 7 / 33 |
v1.619.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.619.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.617.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.615.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.614.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.
v1.613.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.