@chakra-ui/modal
An accessible dialog (modal) 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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are official @chakra-ui packages from monorepo refactor. | ai | |
| provenance | missing-githead | AI (provenance): Publish hygiene only; consistent trusted maintainer, no behavior change. | ai | |
| phantom-deps | phantom-dep:react-remove-scroll | AI (phantom-deps): Standard modal scroll-lock dep, common false positive in bundled builds. | ai | |
| phantom-deps | phantom-dep:aria-hidden | AI (phantom-deps): Used internally by focus-lock/modal logic; likely bundled, false positive from static import scan. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/hooks | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/utils | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/portal | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/focus-lock | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/transition | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-utils | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/close-button | AI (phantom-deps): Same-org monorepo sibling package, expected dependency. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-types | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/close-button | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/shared-utils | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-context | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-merge-refs | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/transition | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/portal | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@chakra-ui/focus-lock | AI (dependencies): First-party Chakra UI monorepo sub-package; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 10 / 8 | |
| 2.3.0 | 10 / 8 | |
| 2.2.12 | 10 / 8 | |
| 2.2.11 | 10 / 8 | |
| 2.2.10 | 10 / 8 | |
| 2.2.9 | 10 / 8 | |
| 2.2.8 | 10 / 8 | |
| 2.2.7 | 10 / 8 | |
| 2.2.6 | 10 / 8 | |
| 2.2.5 | 9 / 9 | |
| 2.2.4 | 9 / 9 | |
| 2.2.3 | 9 / 9 | |
| 2.2.2 | 9 / 9 | |
| 2.2.1 | 9 / 9 | |
| 2.2.0 | 9 / 8 | |
| 2.1.7 | 9 / 8 | |
| 2.1.6 | 9 / 6 | |
| 2.1.5 | 9 / 6 | |
| 2.1.4 | 9 / 6 | |
| 2.1.3 | 9 / 6 | |
| 2.1.2 | 9 / 4 | |
| 2.1.1 | 9 / 4 | |
| 2.1.0 | 9 / 4 | |
| 2.0.3 | 9 / 4 | |
| 2.0.2 | 9 / 4 | |
| 2.0.1 | 9 / 4 | |
| 2.0.0 | 9 / 4 |
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.