Package status › is request still maintained?
Deprecatedrequest 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 | 11 February 2020 (about 6 years ago) |
| Latest version | 2.88.2 |
| Weekly downloads | 13,178,895 |
| Deprecation flag (npm) | Yes |
| Maintainer’s note | "request has been deprecated, see https://github.com/request/request/issues/3142" |
| Maintainers listed | 4 |
| Total releases | 126 |
| Source repository | https://github.com/request/request |
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.
requestnpm reports that request 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: "request has been deprecated, see https://github.com/request/request/issues/3142" 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.