Is commander healthy, maintained, and safe?
Yes — commander looks healthy, actively maintained, and free of known advisories today.
The verdict
OSPulse scores commander at 95/100 (minimal risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Yes — commander looks healthy, actively maintained, and free of known advisories today.
Its most recent release shipped on 29 May 2026 — 61 days ago — so development is clearly active. Across 125 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Two maintainers are listed; better than a lone author, but still a thin bench if one steps away.
On the security side, OSV has no advisories on record for commander today. That's reassuring, but "no known advisory" is not the same as "no vulnerability" — it only means nothing has been disclosed and indexed yet.
The signals are green today, but a clean snapshot is not a standing guarantee — packages drift. 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
- v15.0.0
- Last release
- 29 May 2026 (61 days ago)
- Total releases
- 125
- First release
- 14 August 2011
- Package age
- 15.0 years
- Maintainers
- 2
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is commander still maintained?
Yes — commander released as recently as 29 May 2026 (61 days ago), so it is actively maintained.
Does commander have known security vulnerabilities?
No advisories are currently recorded for commander in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is commander safe to use?
Yes — commander looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 95/100 (minimal risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
commander 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-07-28 · scores are deterministic and recomputed on each refresh.