@inquirer/password
Inquirer password 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted long-standing maintainer (sboudrias) with 1280 approved packages; gitHead is actually present in package.json; likely a CI/CD environment change, not a supply chain concern. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to the v2 rewrite adding dual ESM/CJS compiled output and inlining core logic previously delegated to @inquirer/input; no injected payload indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ansi-escapes is a well-known, legitimate CLI utility package; its addition is consistent with a terminal password prompt's functionality and poses no security risk. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a legitimate, well-known utility for CLI prompt libraries; appropriate dependency for this package. | ai | |
| dependencies | unvetted-dep:@inquirer/ansi | AI (dependencies): First-party dependency within the @inquirer monorepo, published by the same author (sboudrias). | ai | |
| typosquat | typosquat.levenshtein:passport | AI (typosquat): @inquirer/password is part of the official Inquirer.js monorepo; scoped namespace and clear purpose rule out brand impersonation. | ai | |
| dependencies | unvetted-dep:@inquirer/type | AI (dependencies): First-party dependency within the @inquirer monorepo, published by the same author (sboudrias). | ai | |
| dependencies | unvetted-dep:@inquirer/core | AI (dependencies): First-party dependency within the @inquirer monorepo, published by the same author (sboudrias). | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 3 / 2 | |
| 5.1.0 | 3 / 2 | |
| 5.0.13 | 3 / 2 | |
| 5.0.12 | 3 / 2 | |
| 5.0.11 | 3 / 2 | |
| 5.0.10 | 3 / 2 | |
| 5.0.9 | 3 / 2 | |
| 5.0.8 | 3 / 3 | |
| 5.0.7 | 3 / 3 | |
| 5.0.6 | 3 / 3 | |
| 5.0.5 | 3 / 3 | |
| 5.0.4 | 3 / 3 | |
| 5.0.3 | 3 / 3 | |
| 5.0.2 | 3 / 3 | |
| 5.0.1 | 3 / 3 | |
| 5.0.0 | 3 / 3 | |
| 4.0.23 | 3 / 4 | |
| 4.0.22 | 3 / 4 | |
| 4.0.21 | 3 / 4 | |
| 4.0.20 | 3 / 4 | |
| 4.0.19 | 3 / 4 | |
| 4.0.18 | 3 / 4 | |
| 4.0.17 | 3 / 4 | |
| 4.0.16 | 3 / 4 | |
| 4.0.15 | 3 / 4 | |
| 4.0.14 | 3 / 4 | |
| 4.0.13 | 3 / 4 | |
| 4.0.12 | 3 / 4 | |
| 4.0.11 | 3 / 4 | |
| 4.0.10 | 3 / 4 | |
| 4.0.9 | 3 / 4 | |
| 4.0.8 | 3 / 4 | |
| 4.0.7 | 3 / 4 | |
| 4.0.6 | 3 / 4 | |
| 4.0.5 | 3 / 4 | |
| 4.0.4 | 3 / 4 | |
| 4.0.3 | 3 / 4 | |
| 4.0.2 | 3 / 4 | |
| 4.0.1 | 3 / 4 | |
| 4.0.0 | 3 / 4 | |
| 3.0.1 | 3 / 1 | |
| 3.0.0 | 3 / 1 | |
| 2.2.0 | 3 / 1 | |
| 2.1.22 | 3 / 1 | |
| 2.1.21 | 3 / 1 | |
| 2.1.20 | 3 / 1 | |
| 2.1.19 | 3 / 1 | |
| 2.1.18 | 3 / 1 | |
| 2.1.17 | 3 / 1 | |
| 2.1.16 | 3 / 1 | |
| 2.1.15 | 3 / 1 |
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
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.
v4.0.18
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.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
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.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
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.
v4.0.13
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.
v4.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.