← Home

@salutejs/plasma-web

npm Repository Homepage

Salute Design System / React UI kit for web applications

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

salute-evaawinogradovturanchokssalute-assistant

Keywords

design-systemreact-componentsui-kitreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@salutejs/plasma-tokens-b2c AI (dependencies): Same-org (@salutejs) token package; consistent pattern across this monorepo's releases. ai
dependencies unvetted-dep:@salutejs/plasma-tokens-web AI (dependencies): Same-org (@salutejs) token package; consistent pattern across this monorepo's releases. ai
provenance no-provenance AI (provenance): Large established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. ai
phantom-deps phantom-dep:@salutejs/plasma-typo AI (phantom-deps): Same-org monorepo dep; may be re-exported transitively rather than directly imported. ai
phantom-deps phantom-dep:@salutejs/plasma-tokens-b2b AI (phantom-deps): Same-org monorepo dep; consistent with design-token re-export pattern. ai
phantom-deps phantom-dep:@salutejs/plasma-tokens-b2c AI (phantom-deps): Same-org monorepo dep; consistent with design-token re-export pattern. ai

Versions (showing 7 of 7)

Version Deps Published
1.621.1 8 / 30
1.621.0 8 / 30
1.619.0 8 / 31
1.618.0 8 / 31
1.617.0 8 / 31
1.616.0 8 / 31
1.615.0 8 / 31

v1.621.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.621.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.619.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.617.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.616.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.615.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.