@radix-ui/react-direction
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): vladmoroz is a known Radix UI team maintainer; publisher transitions within the radix-ui org are expected and legitimate for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI primitives packages consistently lack descriptions/keywords; spam-flagged maintainers are known Radix UI contributors. These are structural false positives for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix UI primitives monorepo packages consistently omit descriptions; this is a known publishing pattern for this ecosystem, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI packages in this version range do not use Sigstore provenance; absence is consistent across the entire primitives monorepo and not a risk indicator here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 0 / 8 | |
| 1.1.0 | 0 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 1.1.2-rc.1766004502650 | 0 / 9 | |
| 1.1.2-rc.1762291353631 | 0 / 9 |
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2024-06-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.