@inquirer/prompts
Inquirer prompts, combined in a single package
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established package by long-standing maintainer; gitHead is present in package.json; provenance gap is a hygiene concern, not a compromise indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Inquirer.js is a well-established ecosystem package; lack of Sigstore attestation is a hygiene gap but not a risk signal given the publisher's track record. | ai | |
| phantom-deps | phantom-dep:@inquirer/input | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/editor | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/expand | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/number | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/search | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/select | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/confirm | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/rawlist | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/checkbox | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| phantom-deps | phantom-dep:@inquirer/password | AI (phantom-deps): Aggregator package re-exporting @inquirer prompts; phantom-dep is expected for facade packages. | ai | |
| dependencies | unvetted-dep:@inquirer/number | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/search | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/select | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/confirm | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/rawlist | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/password | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/expand | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/input | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/editor | AI (dependencies): First-party dep from same @inquirer monorepo by same maintainer (sboudrias). Stable for this package. | ai |
Versions (showing 100 of 111)
| Version | Deps | Published |
|---|---|---|
| 8.5.1 | 10 / 3 | |
| 8.5.0 | 10 / 3 | |
| 8.4.3 | 10 / 3 | |
| 8.4.2 | 10 / 3 | |
| 8.4.1 | 10 / 3 | |
| 8.4.0 | 10 / 3 | |
| 8.3.2 | 10 / 3 | |
| 8.3.1 | 10 / 3 | |
| 8.3.0 | 10 / 3 | |
| 8.2.1 | 10 / 3 | |
| 8.2.0 | 10 / 3 | |
| 8.1.0 | 10 / 3 | |
| 8.0.2 | 10 / 3 | |
| 8.0.1 | 10 / 3 | |
| 8.0.0 | 10 / 3 | |
| 7.10.1 | 10 / 4 | |
| 7.10.0 | 10 / 4 | |
| 7.9.0 | 10 / 4 | |
| 7.8.6 | 10 / 4 | |
| 7.8.5 | 10 / 4 | |
| 7.8.4 | 10 / 4 | |
| 7.8.3 | 10 / 4 | |
| 7.8.2 | 10 / 4 | |
| 7.8.1 | 10 / 4 | |
| 7.8.0 | 10 / 4 | |
| 7.7.1 | 10 / 4 | |
| 7.7.0 | 10 / 4 | |
| 7.6.0 | 10 / 4 | |
| 7.5.3 | 10 / 4 | |
| 7.5.2 | 10 / 4 | |
| 7.5.1 | 10 / 4 | |
| 7.5.0 | 10 / 4 | |
| 7.4.1 | 10 / 4 | |
| 7.4.0 | 10 / 4 | |
| 7.3.3 | 10 / 4 | |
| 7.3.2 | 10 / 4 | |
| 7.3.1 | 10 / 4 | |
| 7.3.0 | 10 / 4 | |
| 7.2.4 | 10 / 4 | |
| 7.2.3 | 10 / 4 | |
| 7.2.2 | 10 / 4 | |
| 7.2.1 | 10 / 4 | |
| 7.2.0 | 10 / 4 | |
| 7.1.0 | 10 / 4 | |
| 7.0.1 | 10 / 4 | |
| 7.0.0 | 10 / 4 | |
| 6.0.1 | 10 / 1 | |
| 6.0.0 | 10 / 1 | |
| 5.5.0 | 10 / 1 | |
| 5.4.0 | 10 / 1 | |
| 5.3.8 | 10 / 1 | |
| 5.3.7 | 10 / 1 | |
| 5.3.6 | 10 / 1 | |
| 5.3.5 | 10 / 1 | |
| 5.3.4 | 10 / 1 | |
| 5.3.3 | 10 / 1 | |
| 5.3.2 | 10 / 1 | |
| 5.3.1 | 10 / 1 | |
| 5.3.0 | 10 / 1 | |
| 5.2.1 | 9 / 1 | |
| 5.2.0 | 9 / 1 | |
| 5.1.3 | 9 / 1 | |
| 5.1.2 | 9 / 1 | |
| 5.1.1 | 9 / 1 | |
| 5.1.0 | 9 / 1 | |
| 5.0.7 | 8 / 1 | |
| 5.0.6 | 8 / 1 | |
| 5.0.5 | 8 / 1 | |
| 5.0.4 | 8 / 1 | |
| 5.0.3 | 8 / 1 | |
| 5.0.2 | 8 / 1 | |
| 5.0.1 | 8 / 1 | |
| 5.0.0 | 8 / 1 | |
| 4.3.3 | 9 / 0 | |
| 4.3.2 | 9 / 0 | |
| 4.3.1 | 9 / 0 | |
| 4.3.0 | 9 / 0 | |
| 4.2.1 | 9 / 0 | |
| 4.2.0 | 9 / 0 | |
| 4.1.0 | 9 / 0 | |
| 4.0.0 | 9 / 0 | |
| 3.3.2 | 9 / 0 | |
| 3.3.1 | 9 / 0 | |
| 3.3.0 | 9 / 0 | |
| 3.2.0 | 9 / 0 | |
| 3.1.2 | 9 / 0 | |
| 3.1.1 | 9 / 0 | |
| 3.1.0 | 9 / 0 | |
| 3.0.4 | 9 / 0 | |
| 3.0.3 | 9 / 0 | |
| 3.0.2 | 9 / 0 | |
| 3.0.1 | 9 / 0 | |
| 3.0.0 | 9 / 0 | |
| 2.3.1 | 9 / 0 | |
| 2.3.0 | 9 / 0 | |
| 2.2.0 | 9 / 0 | |
| 2.1.1 | 9 / 0 | |
| 2.1.0 | 9 / 0 | |
| 2.0.0 | 9 / 0 | |
| 1.2.3 | 9 / 0 |
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
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.2
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.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sboudrias.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.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.2.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.1.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.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.
v3.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.
v3.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.
v3.3.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.
v3.2.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.
v3.1.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.
v3.1.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.
v3.1.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.
v3.0.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.
v3.0.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.
v3.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.
v3.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.
v3.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.
v2.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.
v2.3.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.
v2.2.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.
v2.1.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.
v2.1.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.
v2.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.
v1.2.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.