@heroui/accordion
Collapse display a list of high-level options that can expand/collapse to reveal more information.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established HeroUI org package; missing provenance is a process gap, not a security risk for this publisher. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 42 approved packages in the HeroUI org; dormancy likely reflects project cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@react-types/accordion | AI (dependencies): @react-types/accordion is a standard React Aria types package used throughout the HeroUI ecosystem; alpha versioning is expected for this type. | ai | |
| phantom-deps | phantom-dep:@react-aria/button | AI (phantom-deps): @react-aria/button is a listed dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.2.28 | 13 / 0 | |
| 2.2.26 | 13 / 0 | |
| 2.2.23 | 13 / 0 | |
| 2.2.19 | 14 / 0 | |
| 2.2.17 | 15 / 0 | |
| 2.2.16 | 15 / 0 | |
| 2.2.15 | 15 / 0 | |
| 2.2.14 | 15 / 0 | |
| 2.2.13 | 15 / 0 | |
| 2.2.12 | 15 / 0 | |
| 2.2.11 | 15 / 0 | |
| 2.2.8 | 15 / 0 | |
| 2.2.7 | 15 / 0 |
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.