Is nodemon healthy, maintained, and safe?
Yes — nodemon looks healthy, actively maintained, and free of known advisories today.
The verdict
OSPulse scores nodemon at 80/100 (minimal risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Yes — nodemon looks healthy, actively maintained, and free of known advisories today.
The last release was 20 February 2026 (156 days ago); still within a normal window, but the cadence has quietened. Across 265 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
On the security side, OSV has no advisories on record for nodemon 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
- v3.1.14
- Last release
- 20 February 2026 (156 days ago)
- Total releases
- 265
- First release
- 3 February 2011
- Package age
- 15.5 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is nodemon still maintained?
Partly — the most recent release was 20 February 2026 (156 days ago), so maintenance has slowed but not fully stopped.
Does nodemon have known security vulnerabilities?
No advisories are currently recorded for nodemon in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is nodemon safe to use?
Yes — nodemon looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 80/100 (minimal risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
nodemon 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-27 · scores are deterministic and recomputed on each refresh.