← Home

@radix-ui/react-collapsible

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/components/collapsible).

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

benoitgrelardstephenhaneyandy-hookhadihallakchancestricklandmark-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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): Reflects organizational transition at Radix/WorkOS; expected. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy due to monorepo restructuring; not suspicious for this package. ai
bogus-package bogus-package AI (bogus-package): Radix UI primitives are well-known; sparse README is normal for scoped sub-packages. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.12 8 / 9
1.1.11 8 / 9
1.1.10 8 / 9
1.1.9 8 / 9
1.0.3 9 / 0

v1.1.12

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.

v1.1.11

2 findings
HIGH Publisher changed: benoitgrelard → chancestrickland (on 2025-05-20) provenance

This 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.

LOW No provenance attestation provenance

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

v1.1.10

2 findings
HIGH Publisher changed: benoitgrelard → chancestrickland (on 2025-05-06) provenance

This 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.

LOW No provenance attestation provenance

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

v1.1.9

2 findings
HIGH Publisher changed: benoitgrelard → chancestrickland (on 2025-05-05) provenance

This 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.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.