← Home

@salutejs/sdds-sbcom

npm Repository Homepage

Salute Design System / React UI kit for SDDS SBCOM web applications

15
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

salute-evaawinogradovturanchokssalute-assistant

Keywords

design-systemreact-componentsreactui-kit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@salutejs-ds/sdds_sbcom AI (dependencies): Internal design system dependency from the same org; stable pattern across versions. ai
provenance no-provenance AI (provenance): Salute Design System packages consistently lack provenance; stable false positive for this publisher. ai
phantom-deps phantom-dep:@salutejs-ds/sdds_sbcom AI (phantom-deps): Config-only reference in a design system package; stable false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.358.0 2 / 32
0.356.0 2 / 32
0.355.0 2 / 32
0.353.0 2 / 32
0.351.1 2 / 32
0.351.0 2 / 32
0.349.0 2 / 32
0.348.0 2 / 32
0.346.0 2 / 32
0.345.0 2 / 32
0.344.0 2 / 32
0.343.0 2 / 33
0.342.0 2 / 33
0.341.0 2 / 33
0.340.0 2 / 33

v0.358.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.

v0.356.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.

v0.343.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.

v0.342.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.

v0.341.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.

v0.340.0

1 finding
INFO No provenance attestation provenance

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