@chakra-ui/react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): v3 monorepo consolidation bundles previously separate @chakra-ui/* sub-packages into one; size increase is expected. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Same rationale: v2→v3 architectural rewrite consolidates many packages; dramatic size increase is structural, not injected payload. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 288-day gap corresponds to the documented v3 development period; not indicative of account takeover for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@ark-ui/react, @emotion/*, @pandacss/is-valid-prop, csstype) are all well-known, established packages matching v3's documented architecture. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 3.35.0 | 7 / 5 | |
| 3.34.0 | 7 / 5 | |
| 3.33.0 | 7 / 5 | |
| 3.32.0 | 7 / 5 | |
| 3.31.0 | 7 / 5 | |
| 3.30.0 | 7 / 5 | |
| 3.29.0 | 7 / 5 | |
| 3.28.1 | 7 / 5 | |
| 3.28.0 | 8 / 4 | |
| 3.27.1 | 8 / 4 | |
| 3.27.0 | 8 / 4 | |
| 3.26.0 | 8 / 4 | |
| 3.25.0 | 8 / 4 | |
| 3.24.2 | 8 / 4 | |
| 3.24.1 | 8 / 4 | |
| 3.24.0 | 8 / 4 | |
| 3.23.0 | 8 / 4 | |
| 3.22.0 | 8 / 4 | |
| 3.21.1 | 8 / 4 | |
| 3.21.0 | 8 / 4 | |
| 3.20.0 | 8 / 4 | |
| 3.19.2 | 8 / 4 | |
| 3.19.1 | 8 / 4 | |
| 3.19.0 | 8 / 4 | |
| 3.18.0 | 8 / 4 | |
| 3.17.0 | 8 / 4 | |
| 3.16.1 | 8 / 4 | |
| 3.16.0 | 8 / 4 | |
| 3.15.1 | 8 / 4 | |
| 3.15.0 | 8 / 4 | |
| 3.14.2 | 8 / 4 | |
| 3.14.1 | 8 / 4 | |
| 3.14.0 | 8 / 4 | |
| 3.13.0 | 8 / 4 | |
| 3.12.0 | 8 / 4 | |
| 3.11.0 | 8 / 4 | |
| 3.10.0 | 8 / 4 | |
| 3.9.0 | 8 / 4 | |
| 3.8.2 | 8 / 4 | |
| 3.8.1 | 8 / 4 | |
| 3.8.0 | 7 / 4 | |
| 3.7.0 | 7 / 4 | |
| 3.6.0 | 7 / 4 | |
| 3.5.1 | 7 / 4 | |
| 3.5.0 | 7 / 4 | |
| 3.4.0 | 7 / 4 | |
| 3.3.3 | 7 / 4 | |
| 3.3.2 | 7 / 4 | |
| 3.3.1 | 7 / 4 | |
| 3.3.0 | 7 / 4 | |
| 3.2.5 | 7 / 4 |
v3.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.