@chakra-ui/popover
A React component to render that renders its content in a popover
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 release tooling variance, not a behavior signal; trusted publisher with long track record. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Normal monorepo release cadence for this package/publisher, no other malicious indicators. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/hooks | AI (phantom-deps): Same-org monorepo sibling, standard workspace dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/utils | AI (phantom-deps): Same-org monorepo sibling, standard workspace dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/popper | AI (phantom-deps): Same-org monorepo sibling, standard workspace dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-utils | AI (phantom-deps): Same-org monorepo sibling, standard workspace dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/close-button | AI (phantom-deps): Same-org monorepo sibling, standard workspace dependency. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-merge-refs | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-focus-effect | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/popper | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-focus-on-pointer-down | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Chakra UI predates Sigstore provenance; consistent across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-animation-state | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/lazy-utils | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-types | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/close-button | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/shared-utils | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-context | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-disclosure | AI (dependencies): Internal Chakra UI monorepo sub-package; stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 11 / 10 | |
| 2.2.0 | 11 / 10 | |
| 2.1.12 | 11 / 10 | |
| 2.1.11 | 11 / 10 | |
| 2.1.10 | 11 / 10 | |
| 2.1.9 | 11 / 10 | |
| 2.1.8 | 11 / 10 | |
| 2.1.7 | 11 / 10 | |
| 2.1.6 | 11 / 10 | |
| 2.1.5 | 11 / 10 | |
| 2.1.4 | 10 / 11 | |
| 2.1.3 | 10 / 11 | |
| 2.1.2 | 10 / 11 | |
| 2.1.1 | 10 / 11 | |
| 2.1.0 | 10 / 10 | |
| 2.0.9 | 8 / 9 | |
| 2.0.8 | 5 / 8 | |
| 2.0.7 | 5 / 8 | |
| 2.0.6 | 5 / 8 | |
| 2.0.5 | 5 / 8 | |
| 2.0.4 | 5 / 3 | |
| 2.0.3 | 5 / 3 | |
| 2.0.2 | 5 / 3 | |
| 2.0.1 | 5 / 3 | |
| 2.0.0 | 5 / 3 |
v2.2.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.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
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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.