Package status › is jade still maintained?
Deprecatedjade still maintained?The maintainers have marked this package as deprecated on npm. Here's the registry evidence, and what it means if this package is in your stack.
| Verdict | Deprecated |
|---|---|
| Last release on npm | 12 June 2015 (about 11 years ago) |
| Latest version | 1.11.0 |
| Weekly downloads | 388,455 |
| Deprecation flag (npm) | Yes |
| Maintainer’s note | "Jade has been renamed to pug, please install the latest version of pug instead of jade" |
| Maintainers listed | 1 |
| Total releases | 131 |
| Source repository | https://github.com/jadejs/jade |
Source: npm registry and npm downloads API, read on 18 July 2026. We report only what the registry publishes — we don't infer repository activity.
jadenpm reports that jade is deprecated by its maintainers. That flag is the strongest signal a registry gives: the people who publish it are telling you to stop using it. Their own note reads: "Jade has been renamed to pug, please install the latest version of pug instead of jade" If that note names a replacement, that is your migration target. Pin your current version so nothing shifts under you, then plan the move on your own schedule rather than waiting for a build to break.
Deprely watches npm deprecation flags and published API sunset notices, then emails your team one short heads-up — before a build breaks. No dashboard to check.
First alerts planned for autumn 2026. One email when we open — no spam.