@inquirer/core
Core Inquirer prompt API
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 | source-size-dropped | AI (source-diff): Package ships only compiled dist/ output; source size drop is an artifact of the diff baseline, not a real stub/redirect replacement. | ai | |
| phantom-deps | phantom-dep:run-async | AI (phantom-deps): run-async is a declared runtime dependency used for async task execution; phantom-dep finding is a false positive for utility libraries. | ai | |
| dependencies | unvetted-dep:figures | AI (dependencies): figures is a well-known Sindre Sorhus package for terminal symbols; its use in a CLI prompt library is expected and benign. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a TypeScript type package loaded by convention; not a real phantom dependency risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/wrap-ansi | AI (phantom-deps): @types/wrap-ansi is a TypeScript type package; its presence as a declared but not directly imported dep is expected and benign. | ai | |
| phantom-deps | phantom-dep:@types/mute-stream | AI (phantom-deps): @types/mute-stream is a TypeScript type package; its presence as a declared but not directly imported dep is expected and benign. | ai | |
| dependencies | unvetted-dep:@types/wrap-ansi | AI (dependencies): @types/wrap-ansi is a TypeScript type definition package with no executable runtime code; it poses no security risk and is a stable dependency for this package. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a legitimate, widely-used ANSI escape code utility; appropriate for a CLI prompt library. | ai | |
| phantom-deps | phantom-dep:@inquirer/figures | AI (phantom-deps): Same-org monorepo dependency; terminal figures/symbols for UI rendering. | ai | |
| phantom-deps | phantom-dep:fast-wrap-ansi | AI (phantom-deps): New dependency for ANSI text wrapping; legitimate utility for terminal output formatting. | ai | |
| phantom-deps | phantom-dep:cli-width | AI (phantom-deps): Legitimate runtime dependency for CLI width detection; indirectly used through package modules. | ai | |
| phantom-deps | phantom-dep:mute-stream | AI (phantom-deps): Legitimate runtime dependency for stream muting in terminal I/O; indirectly used. | ai | |
| phantom-deps | phantom-dep:signal-exit | AI (phantom-deps): Legitimate runtime dependency for signal handling; indirectly used through package modules. | ai | |
| phantom-deps | phantom-dep:@inquirer/ansi | AI (phantom-deps): Same-org monorepo dependency; core ANSI utilities for terminal rendering. | ai | |
| phantom-deps | phantom-dep:@inquirer/type | AI (phantom-deps): Same-org monorepo dependency; type definitions used by core prompt API. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dependency swap from wrap-ansi to fast-wrap-ansi is a benign substitution by a trusted, long-standing publisher with a strong track record. | ai | |
| dependencies | unvetted-dep:cli-width | AI (dependencies): cli-width is a long-standing utility dependency of Inquirer.js; no security concern. | ai | |
| dependencies | unvetted-dep:mute-stream | AI (dependencies): mute-stream is a long-standing utility dependency of Inquirer.js; no security concern. | ai | |
| dependencies | unvetted-dep:@inquirer/figures | AI (dependencies): @inquirer/figures is a first-party package from the same Inquirer.js monorepo by sboudrias. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @inquirer/core in official Inquirer.js namespace; clearly distinct from unscoped 'cors'. | ai | |
| dependencies | unvetted-dep:@inquirer/type | AI (dependencies): @inquirer/type is a first-party type package from the same Inquirer.js monorepo by sboudrias. | ai | |
| dependencies | unvetted-dep:fast-wrap-ansi | AI (dependencies): fast-wrap-ansi is a minor utility dependency with a reasonable version constraint; no material risk. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 11.2.1 | 7 / 4 | |
| 11.2.0 | 7 / 4 | |
| 11.1.10 | 7 / 4 | |
| 11.1.9 | 7 / 4 | |
| 11.1.8 | 7 / 4 | |
| 11.1.7 | 7 / 4 | |
| 11.1.6 | 7 / 4 | |
| 11.1.5 | 7 / 5 | |
| 11.1.4 | 7 / 5 | |
| 11.1.3 | 7 / 5 | |
| 11.1.2 | 7 / 5 | |
| 11.1.1 | 7 / 5 | |
| 11.1.0 | 7 / 5 | |
| 11.0.2 | 7 / 5 | |
| 11.0.1 | 7 / 5 | |
| 11.0.0 | 7 / 5 | |
| 10.3.2 | 8 / 7 | |
| 10.3.1 | 8 / 7 | |
| 10.3.0 | 8 / 7 | |
| 10.2.2 | 8 / 7 | |
| 10.1.10 | 8 / 7 | |
| 10.1.9 | 8 / 7 | |
| 10.1.8 | 8 / 7 | |
| 10.1.7 | 8 / 7 | |
| 10.1.6 | 8 / 7 | |
| 10.1.5 | 8 / 7 | |
| 10.1.4 | 9 / 7 | |
| 10.1.3 | 9 / 7 | |
| 10.1.2 | 9 / 7 | |
| 10.1.1 | 9 / 7 | |
| 10.1.0 | 9 / 7 | |
| 10.0.1 | 9 / 7 | |
| 10.0.0 | 9 / 7 | |
| 9.2.1 | 12 / 1 | |
| 9.2.0 | 12 / 1 | |
| 9.1.0 | 13 / 1 | |
| 9.0.10 | 13 / 1 | |
| 9.0.9 | 13 / 1 | |
| 9.0.8 | 13 / 1 | |
| 9.0.7 | 13 / 1 | |
| 9.0.6 | 13 / 1 | |
| 9.0.5 | 13 / 1 | |
| 9.0.4 | 13 / 1 | |
| 9.0.3 | 13 / 1 | |
| 9.0.2 | 13 / 1 | |
| 9.0.1 | 13 / 1 | |
| 9.0.0 | 13 / 1 | |
| 8.2.4 | 13 / 1 | |
| 8.2.3 | 13 / 1 | |
| 8.2.2 | 13 / 1 | |
| 8.2.1 | 13 / 1 | |
| 8.2.0 | 13 / 1 | |
| 8.1.0 | 13 / 1 | |
| 8.0.1 | 13 / 1 | |
| 8.0.0 | 13 / 1 | |
| 7.1.3 | 13 / 1 | |
| 7.1.2 | 13 / 1 | |
| 7.1.1 | 13 / 1 | |
| 7.1.0 | 14 / 1 | |
| 7.0.2 | 14 / 1 | |
| 7.0.1 | 14 / 1 | |
| 7.0.0 | 14 / 1 | |
| 6.0.0 | 14 / 1 | |
| 5.1.2 | 14 / 1 | |
| 5.1.1 | 14 / 1 | |
| 5.1.0 | 14 / 1 | |
| 5.0.1 | 14 / 1 | |
| 5.0.0 | 14 / 1 | |
| 4.1.0 | 14 / 1 | |
| 4.0.0 | 13 / 1 | |
| 3.1.2 | 13 / 1 | |
| 3.1.1 | 13 / 1 | |
| 3.1.0 | 13 / 1 | |
| 3.0.0 | 14 / 1 | |
| 2.3.1 | 14 / 1 | |
| 2.3.0 | 11 / 1 | |
| 2.2.0 | 11 / 1 | |
| 2.1.0 | 11 / 1 | |
| 2.0.0 | 11 / 1 | |
| 1.3.0 | 11 / 1 | |
| 1.2.2 | 11 / 1 | |
| 1.2.1 | 11 / 1 | |
| 1.2.0 | 11 / 1 | |
| 1.1.3 | 11 / 1 | |
| 1.1.2 | 11 / 1 | |
| 1.1.0 | 11 / 1 | |
| 1.0.4 | 11 / 1 | |
| 1.0.3 | 11 / 1 | |
| 1.0.2 | 11 / 1 | |
| 1.0.1 | 11 / 2 | |
| 1.0.0 | 11 / 2 |
v11.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
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.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.