@inquirer/checkbox
Inquirer checkbox prompt
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:figures | AI (dependencies): figures is a well-known terminal symbols package, its use in a CLI prompt component like @inquirer/checkbox is expected and benign. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dependency swap from picocolors to yoctocolors-cjs is routine maintenance; both are legitimate color utilities with no malicious indicators. | ai | |
| dependencies | unvetted-dep:@inquirer/ansi | AI (dependencies): First-party sibling package in the @inquirer/ namespace, maintained by the same publisher (sboudrias). Not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@inquirer/core | AI (dependencies): First-party sibling package in the @inquirer/ namespace, maintained by the same publisher (sboudrias). Not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@inquirer/type | AI (dependencies): First-party sibling package in the @inquirer/ namespace, maintained by the same publisher (sboudrias). Not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@inquirer/figures | AI (dependencies): First-party sibling package in the @inquirer/ namespace, maintained by the same publisher (sboudrias). Not a third-party unknown. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a standard, widely-used ANSI escape code library; transitive dependency through established @inquirer packages. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is a best-practice recommendation; absence is not a security blocker for an established, trusted publisher. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 5.2.1 | 4 / 2 | |
| 5.2.0 | 4 / 2 | |
| 5.1.5 | 4 / 2 | |
| 5.1.4 | 4 / 2 | |
| 5.1.3 | 4 / 2 | |
| 5.1.2 | 4 / 2 | |
| 5.1.1 | 4 / 2 | |
| 5.1.0 | 4 / 3 | |
| 5.0.7 | 4 / 3 | |
| 5.0.6 | 4 / 3 | |
| 5.0.5 | 4 / 3 | |
| 5.0.4 | 4 / 3 | |
| 5.0.3 | 4 / 3 | |
| 5.0.2 | 4 / 3 | |
| 5.0.1 | 4 / 3 | |
| 5.0.0 | 4 / 3 | |
| 4.3.2 | 5 / 4 | |
| 4.3.1 | 5 / 4 | |
| 4.3.0 | 5 / 4 | |
| 4.2.4 | 5 / 4 | |
| 4.1.5 | 5 / 4 | |
| 4.1.4 | 5 / 4 | |
| 4.1.3 | 5 / 4 | |
| 4.1.2 | 5 / 4 | |
| 4.1.1 | 5 / 4 | |
| 4.1.0 | 5 / 4 | |
| 4.0.7 | 5 / 4 | |
| 4.0.6 | 5 / 4 | |
| 4.0.5 | 5 / 4 | |
| 4.0.4 | 5 / 4 | |
| 4.0.3 | 5 / 4 | |
| 4.0.2 | 5 / 4 | |
| 4.0.1 | 5 / 4 | |
| 4.0.0 | 5 / 4 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 | |
| 2.5.0 | 5 / 1 | |
| 2.4.7 | 5 / 1 | |
| 2.4.6 | 5 / 1 | |
| 2.4.5 | 5 / 1 | |
| 2.4.4 | 5 / 1 | |
| 2.4.3 | 5 / 1 | |
| 2.4.2 | 5 / 1 | |
| 2.4.1 | 5 / 1 | |
| 2.4.0 | 5 / 1 | |
| 2.3.11 | 5 / 1 | |
| 2.3.10 | 5 / 1 | |
| 2.3.9 | 5 / 1 | |
| 2.3.8 | 5 / 1 | |
| 2.3.7 | 5 / 1 | |
| 2.3.6 | 5 / 1 |
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.
v5.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.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.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.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.