@chakra-ui/react-use-pan-event
React hook to track pan events
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:framesync | AI (phantom-deps): Used dependency, likely missed by import scan due to build output. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/event-utils | AI (phantom-deps): Same-org internal dep, false positive from bundling. | ai | |
| provenance | no-provenance | AI (provenance): Chakra UI packages consistently lack provenance attestation; stable false positive for this publisher. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 3 / 2 | |
| 2.0.9 | 3 / 2 | |
| 2.0.8 | 3 / 2 | |
| 2.0.7 | 3 / 2 | |
| 2.0.6 | 3 / 2 | |
| 2.0.5 | 3 / 2 | |
| 2.0.4 | 2 / 1 | |
| 2.0.3 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.1 | 2 / 1 |
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.