@radix-ui/react-presence
This is an internal utility, not intended for public usage.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): benoitgrelard is a known Radix UI core contributor; the publisher change from jjenzz reflects a legitimate internal team transition within the radix-ui org, stable across versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jjenzz corresponds to the same internal Radix UI team reorganization; not a hostile takeover signal for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard transpilation runtime dependency for Radix UI packages; loaded by convention and not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI sub-packages legitimately have short READMEs, no keywords, and spam-flagged maintainers are Radix UI contributors — false positive for this well-established monorepo package. | ai | |
| provenance | missing-githead | AI (provenance): Established Radix UI package with clean version diff; missing gitHead reflects a publish environment change, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI packages historically publish without Sigstore provenance; no security risk given the established package identity and clean content. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.1.5 | 2 / 9 | |
| 1.1.4 | 2 / 9 | |
| 1.1.3 | 2 / 8 | |
| 1.0.1 | 3 / 0 | |
| 1.0.0 | 3 / 0 | |
| 0.1.2 | 3 / 0 | |
| 0.1.1 | 3 / 0 | |
| 0.1.0 | 3 / 0 | |
| 0.0.15 | 3 / 0 | |
| 0.0.14 | 2 / 0 | |
| 0.0.13 | 2 / 0 | |
| 0.0.12 | 2 / 0 | |
| 0.0.11 | 2 / 0 | |
| 0.0.10 | 2 / 0 | |
| 0.0.9 | 2 / 0 | |
| 0.0.8 | 1 / 0 | |
| 0.0.7 | 1 / 0 | |
| 0.0.6 | 1 / 0 | |
| 0.0.5 | 2 / 0 | |
| 0.0.4 | 2 / 0 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 2 / 0 | |
| 0.0.1 | 2 / 1 | |
| 1.1.5-rc.1761760880074 | 2 / 9 | |
| 1.1.5-rc.1761757765388 | 2 / 9 | |
| 1.1.5-rc.1761752560860 | 2 / 9 | |
| 1.1.5-rc.1761750294484 | 2 / 9 | |
| 1.1.5-rc.1761750045307 | 2 / 9 | |
| 1.1.5-rc.1761621280215 | 2 / 9 | |
| 1.1.5-rc.1761620575619 | 2 / 9 | |
| 1.1.5-rc.1761619701743 | 2 / 9 | |
| 1.1.5-rc.1761615925003 | 2 / 9 | |
| 1.1.5-rc.1761614930803 | 2 / 9 | |
| 1.1.5-rc.1761614469962 | 2 / 9 | |
| 1.1.5-rc.1761582029795 | 2 / 9 | |
| 1.1.5-rc.1761327012562 | 2 / 9 | |
| 1.1.5-rc.1755205432459 | 2 / 9 | |
| 1.1.5-rc.1755201399387 | 2 / 9 | |
| 1.1.5-rc.1755118410828 | 2 / 9 | |
| 1.1.5-rc.1755114563302 | 2 / 9 | |
| 1.1.4-rc.1745339201309 | 2 / 9 |
v1.1.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2023-05-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-07-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.