Inquirer number prompt
86%
Total Score
healthy
Healthy: frequent releases, active repository work, and npm provenance outweigh minor repository and workflow hygiene concerns.
One contributor made about 81% of the 43 recent commits, despite eight contributors being active. That concentration leaves some continuity risk, so it modestly lowers confidence in long-term resilience.
The repository name does not match the package and its README does not mention @inquirer/number. Although a monorepo can explain the name mismatch, the lack of a package mention makes ownership of this specific release less transparent.
All five workflows were analyzed with no untrusted checkouts, script injection, or high-severity findings, and all 32 action references are pinned. One high-confidence low-severity finding reports an ad hoc package installation outside a lockfile, which is a minor reproducibility concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@inquirer/core Version ^12.0.4 | — | — |
@inquirer/type Version 4.2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.