@clack/prompts
Effortlessly build beautiful command-line apps 🪄 [Try the demo](https://stackblitz.com/edit/clack-prompts?file=index.js)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from personal account to GitHub Actions CI/CD with SLSA provenance. This is a healthy maturation pattern for popular packages. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): picocolors is a declared dependency used in the built output (dist/); phantom-dep detection misses bundled imports. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect early-stage utility library in monorepo; 8.3M weekly downloads confirm legitimacy. | ai | |
| phantom-deps | phantom-dep:add | AI (phantom-deps): add is a legitimate npm package; phantom-dep pattern in this context reflects build/indirect usage, not malware. | ai | |
| phantom-deps | phantom-dep:fast-string-width | AI (phantom-deps): Bundled ESM package; deps may be inlined in dist output rather than directly imported in source. Not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:fast-wrap-ansi | AI (phantom-deps): Bundled ESM package; deps may be inlined in dist output rather than directly imported in source. Not a real phantom dep concern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (fast-string-width, fast-wrap-ansi) are narrow ANSI/string utilities appropriate for a CLI prompts library. Package has SLSA provenance and publishes via official CI/CD. | ai | |
| phantom-deps | phantom-dep:sisteransi | AI (phantom-deps): sisteransi is a long-standing dep of this package; phantom detection is a false positive for this bundled ESM package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 2 / 6 | |
| 1.0.1 | 3 / 6 | |
| 1.0.0 | 3 / 6 | |
| 0.11.0 | 3 / 1 | |
| 0.10.1 | 3 / 1 | |
| 0.10.0 | 3 / 1 | |
| 0.9.1 | 3 / 1 | |
| 0.9.0 | 3 / 1 | |
| 0.8.2 | 3 / 1 | |
| 0.8.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.3 | 4 / 1 | |
| 0.6.2 | 4 / 1 | |
| 0.6.1 | 4 / 2 | |
| 0.6.0 | 4 / 2 | |
| 0.5.1 | 4 / 2 | |
| 0.5.0 | 4 / 2 | |
| 0.4.5 | 4 / 2 | |
| 0.4.4 | 4 / 2 | |
| 0.4.3 | 4 / 2 | |
| 0.4.2 | 4 / 2 | |
| 0.4.1 | 4 / 2 | |
| 0.4.0 | 4 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.2.2 | 3 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.1 | 3 / 1 | |
| 0.1.0 | 3 / 1 | |
| 0.0.10 | 3 / 3 | |
| 0.0.9 | 3 / 3 | |
| 0.0.8 | 3 / 3 | |
| 0.0.7 | 3 / 3 | |
| 0.0.6 | 3 / 3 | |
| 0.0.5 | 4 / 3 | |
| 0.0.4 | 4 / 3 | |
| 0.0.3 | 4 / 3 | |
| 0.0.2 | 4 / 3 | |
| 0.0.1 | 4 / 3 |
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.