Is request healthy, maintained, and safe?
No — request looks abandoned and still has open security advisories.
The verdict
OSPulse scores request at 24/100 (high risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — request looks abandoned and still has open security advisories.
The last sign of life was 11 February 2020, more than 6 years ago (2358 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. 4 maintainers are listed on npm, so the project isn't hostage to any single contributor.
OSV lists 2 known advisories for request, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
Treat request 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
Known vulnerabilities (2)
Remote Memory Exposure in request
Server-Side Request Forgery in Request
Key facts
- Latest version
- v2.88.2
- Last release
- 11 February 2020 (2358 days ago)
- Total releases
- 126
- First release
- 22 January 2011
- Package age
- 15.5 years
- Maintainers
- 4
- Known advisories
- 2
- Confidence
- High
Frequently asked
Is request still maintained?
It doesn't appear to be — the last release was 11 February 2020, over two years ago, which usually indicates an abandoned package.
Does request have known security vulnerabilities?
Yes — OSV lists 2 advisories for request. See the advisory list on this page for the OSV/GHSA identifiers.
Is request safe to use?
No — request looks abandoned and still has open security advisories. OSPulse rates it 24/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Alternatives to request
Other npm packages we've checked
request 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.