@chakra-ui/popper
A React component and hooks wrapper for popper.js
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:@popperjs/core | AI (phantom-deps): Core dependency used via built dist, monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-utils | AI (phantom-deps): Same-org internal dependency, standard monorepo usage. | ai | |
| provenance | no-provenance | AI (provenance): Established Chakra UI package; no provenance is common and not a risk for this publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 4 | |
| 3.0.14 | 3 / 4 | |
| 3.0.5 | 2 / 3 | |
| 3.0.3 | 2 / 3 | |
| 3.0.2 | 2 / 1 | |
| 3.0.1 | 2 / 1 | |
| 3.0.0 | 2 / 1 |
v3.0.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.
v3.0.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.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.