← Home

@radix-ui/react-icons

npm

Radix UI React Icon Set

10
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

chancestricklandmark-workosbenoitgrelardstephenhaneyandy-hookhadihallak

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Known Radix UI team transition from vladmoroz to chancestrickland (both WorkOS). ai
maintainer-change maintainer-added AI (maintainer-change): chancestrickland and mark-workos are known WorkOS/Radix team members. ai
maintainer-change maintainer-removed AI (maintainer-change): Legitimate org transition; prior maintainers moved off the package. ai

Versions (showing 10 of 10)

Version Deps Published
1.3.2 0 / 2
1.3.1 0 / 2
1.3.0 0 / 2
1.2.0 0 / 2
1.1.1 0 / 2
1.1.0 0 / 2
1.0.3 0 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

2 findings
MEDIUM Publisher changed: peduarte → vladmoroz (on 2022-02-21, unremoved on npm for 1609d) provenance

This version was published by a different npm account (vladmoroz) than the most recent previously approved version (peduarte) on 2022-02-21. It has since remained available on npm for 1609 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.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.