@chakra-ui/cli
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @chakra-ui/cli is a scoped package from the official Chakra UI org; Levenshtein match to 'joi' is a false positive. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): @types/* packages are type-only and not directly imported; standard for TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@types/cli-table | AI (phantom-deps): @types/* packages are type-only and not directly imported; standard for TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@types/babel__core | AI (phantom-deps): @types/* packages are type-only and not directly imported; standard for TypeScript projects. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.35.0 | 25 / 1 | |
| 3.34.0 | 25 / 1 | |
| 3.33.0 | 24 / 1 | |
| 3.32.0 | 24 / 1 | |
| 3.31.0 | 24 / 1 | |
| 3.30.0 | 24 / 1 | |
| 3.29.0 | 20 / 1 | |
| 3.28.1 | 20 / 1 | |
| 3.28.0 | 20 / 1 | |
| 3.27.1 | 20 / 1 | |
| 3.27.0 | 20 / 1 | |
| 3.26.0 | 19 / 1 | |
| 3.25.0 | 19 / 1 | |
| 3.24.2 | 19 / 1 | |
| 3.24.1 | 19 / 1 | |
| 3.24.0 | 19 / 1 | |
| 3.23.0 | 19 / 1 | |
| 3.22.0 | 19 / 1 | |
| 3.21.1 | 19 / 1 | |
| 3.21.0 | 19 / 1 | |
| 3.20.0 | 19 / 1 | |
| 3.19.2 | 19 / 1 | |
| 3.19.1 | 19 / 1 | |
| 3.19.0 | 19 / 1 | |
| 3.18.0 | 19 / 1 | |
| 3.17.0 | 19 / 1 |
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.