@chakra-ui/accordion
A simple and accessible accordion component for React & Chakra UI
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 | missing-githead | AI (provenance): Monorepo publish quirk from trusted maintainer, no behavioral change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Chakra UI packages publish in lockstep across monorepo; dormancy is benign here. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/icon | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/hooks | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/utils | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/descendant | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/transition | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-utils | AI (phantom-deps): Same-org monorepo dep, re-exported not directly imported. | ai | |
| dependencies | unvetted-dep:@chakra-ui/icon | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/descendant | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/transition | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/shared-utils | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-context | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-merge-refs | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-controllable-state | AI (dependencies): Internal Chakra UI monorepo sibling dep; same trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): Established Chakra UI package predates provenance attestation; absence is expected. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 7 / 8 | |
| 2.3.0 | 7 / 8 | |
| 2.2.0 | 7 / 8 | |
| 2.1.11 | 7 / 8 | |
| 2.1.10 | 7 / 8 | |
| 2.1.9 | 7 / 8 | |
| 2.1.8 | 7 / 8 | |
| 2.1.7 | 7 / 8 | |
| 2.1.6 | 7 / 8 | |
| 2.1.5 | 7 / 8 | |
| 2.1.4 | 6 / 9 | |
| 2.1.3 | 6 / 9 | |
| 2.1.2 | 6 / 9 | |
| 2.1.1 | 6 / 9 | |
| 2.1.0 | 6 / 8 | |
| 2.0.12 | 6 / 8 | |
| 2.0.11 | 6 / 8 | |
| 2.0.10 | 6 / 8 | |
| 2.0.9 | 6 / 8 | |
| 2.0.8 | 6 / 6 | |
| 2.0.7 | 6 / 6 | |
| 2.0.6 | 6 / 3 | |
| 2.0.5 | 6 / 3 | |
| 2.0.4 | 6 / 3 | |
| 2.0.3 | 6 / 3 | |
| 2.0.2 | 6 / 3 | |
| 2.0.1 | 6 / 3 | |
| 2.0.0 | 6 / 3 |
v2.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.