Is jade healthy, maintained, and safe?
Probably not. jade has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
jade earns a health score of 25/100, a high risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not. jade has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 12 June 2015, more than 11 years ago (4113 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. 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 jade 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.
Treat jade 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.11.0
- Last release
- 12 June 2015 (4113 days ago)
- Total releases
- 132
- First release
- 19 December 2010
- Package age
- 15.7 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is jade still maintained?
It doesn't appear to be. The last release was 12 June 2015, over two years ago, which usually indicates an abandoned package.
Does jade have known security vulnerabilities?
No advisories are currently recorded for jade in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is jade safe to use?
Probably not. jade has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 25/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
jade 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-15 · scores are deterministic and recomputed on each refresh.