@radix-ui/react-accordion
View docs [here](https://radix-ui.com/primitives/docs/components/accordion).
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): Known Radix UI team transition to chancestrickland (WorkOS); stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): chancestrickland and mark-workos are known WorkOS/Radix maintainers. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): colmtuite/vladmoroz removal is part of the known Radix org restructuring. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org-wide build migration, not abandonment. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI primitives are well-known; sparse README/keywords is a style choice. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.12 | 9 / 9 | |
| 1.2.11 | 9 / 9 | |
| 1.2.10 | 9 / 9 | |
| 1.2.9 | 9 / 9 | |
| 1.1.2 | 10 / 0 |
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
2 findingsThis version was published by a different npm account than previous versions on 2025-05-20. 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.2.10
2 findingsThis version was published by a different npm account than previous versions on 2025-05-06. 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.2.9
2 findingsThis version was published by a different npm account than previous versions on 2025-05-05. 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.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.