Is q healthy, maintained, and safe?
Probably not. q has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
q earns a health score of 35/100, a high risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not. q has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 19 October 2017, more than 8 years ago (3252 days). By any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Two maintainers are listed, better than a lone author, but still a thin bench if one steps away.
Security-wise, q currently has a clean OSV record, with no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
Treat q as a liability to manage: review the evidence above, pin or patch, and evaluate alternatives. This is a one-time snapshot of a single package. Real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Key facts
- Latest version
- v1.5.1
- Last release
- 19 October 2017 (3252 days ago)
- Total releases
- 76
- First release
- 22 December 2010
- Package age
- 15.7 years
- Maintainers
- 2
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is q still maintained?
It doesn't appear to be. The last release was 19 October 2017, over two years ago, which usually indicates an abandoned package.
Does q have known security vulnerabilities?
No advisories are currently recorded for q in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is q safe to use?
Probably not. q has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 35/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
q is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-09-14 · scores are deterministic and recomputed on each refresh.