← Home

@uiid/indicators

npm Repository Homepage

Status indicators — Alert, Avatar, Badge, Progress, Timeline, and more

27
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

adamfratino

Keywords

uiidreactcomponentsdesign-systemindicatorsalertavatarbadge

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. ai
phantom-deps phantom-dep:@uiid/tokens AI (phantom-deps): Same-org scope; likely re-exported transitively rather than directly imported. ai

Versions (showing 27 of 27)

Version Deps Published
0.0.36 5 / 23
0.0.35 5 / 23
0.0.34 5 / 23
0.0.33 5 / 23
0.0.32 5 / 23
0.0.31 5 / 23
0.0.30 5 / 23
0.0.29 5 / 23
0.0.28 5 / 23
0.0.27 5 / 23
0.0.26 5 / 23
0.0.25 5 / 23
0.0.23 5 / 23
0.0.22 5 / 23
0.0.21 5 / 23
0.0.20 5 / 23
0.0.19 5 / 23
0.0.18 5 / 25
0.0.17 5 / 25
0.0.16 5 / 25
0.0.15 5 / 25
0.0.14 5 / 25
0.0.12 5 / 25
0.0.11 5 / 25
0.0.10 5 / 25
0.0.8 5 / 25
0.0.7 5 / 25

v0.0.36

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.0.35

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.0.34

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.0.33

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.0.32

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.0.31

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.0.30

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.0.29

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.0.28

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.0.27

1 finding
INFO No provenance attestation provenance

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