@salutejs/plasma-sb-utils
Code shared between ui libraries.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@salutejs/plasma-colors | AI (dependencies): Same-org dependency (@salutejs); stable internal package used across the plasma ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Long-established org package; lack of provenance is consistent across all prior versions and is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): @emotion/react is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.227.0 | 6 / 7 | |
| 0.225.0 | 6 / 7 | |
| 0.224.0 | 6 / 7 | |
| 0.223.0 | 6 / 7 | |
| 0.222.0 | 7 / 7 | |
| 0.221.0 | 6 / 7 | |
| 0.220.0 | 6 / 7 | |
| 0.219.0 | 6 / 7 | |
| 0.218.0 | 6 / 7 | |
| 0.217.0 | 6 / 7 | |
| 0.214.0 | 6 / 7 | |
| 0.213.0 | 6 / 7 | |
| 0.212.0 | 6 / 7 | |
| 0.211.0 | 6 / 7 | |
| 0.210.0 | 6 / 7 | |
| 0.209.0 | 3 / 8 | |
| 0.208.0 | 3 / 8 | |
| 0.207.0 | 3 / 8 | |
| 0.206.0 | 3 / 8 | |
| 0.204.0 | 3 / 8 | |
| 0.203.0 | 3 / 8 | |
| 0.202.0 | 3 / 8 | |
| 0.200.0 | 3 / 8 | |
| 0.199.0 | 3 / 8 | |
| 0.198.0 | 3 / 8 | |
| 0.197.0 | 3 / 8 |
v0.227.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.225.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.221.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.220.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.219.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.217.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.214.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.212.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.209.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.208.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.207.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.206.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.204.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.203.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.202.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.200.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.199.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.198.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.197.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.