@radix-ui/rect
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account post-acquisition. | ai | |
| provenance | publisher-changed | AI (provenance): Radix UI moved to GitHub Actions CI/CD publishing under WorkOS; legitimate org transition. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions publish flow omits gitHead; SLSA provenance compensates. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): @radix-ui/rect is 'rectangle' utility, not a typosquat of react. Scoped under @radix-ui with 50M+ weekly downloads. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): rect (rectangle) is a legitimate name; not related to 'next'. Established package in @radix-ui scope. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): rect (rectangle) is a legitimate name; not related to 'jest'. Established package in @radix-ui scope. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Small internal monorepo utility; no-deps/no-keywords/no-description is normal for this kind of package. | ai |
v1.1.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
2 findingsPackage name '@radix-ui/rect' is 1 edit(s) away from popular package 'react'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.