Is requests healthy, maintained, and safe?
Maintained, but watch it — requests has real signals (drift, thin maintenance, or advisories) worth tracking.
The verdict
OSPulse scores requests at 55/100 (medium risk), computed deterministically from live PyPI release history, and the OSV vulnerability database. Maintained, but watch it — requests has real signals (drift, thin maintenance, or advisories) worth tracking.
Its most recent release shipped on 14 May 2026 — 75 days ago — so development is clearly active. Across 158 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. PyPI doesn't expose a reliable maintainer count, so bus-factor isn't scored here — treat maintenance depth as unknown rather than assumed.
OSV lists 16 known advisories for requests, including 1 high. 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.
requests is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. 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 requirements.txt through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (16)
Exposure of Sensitive Information to an Unauthorized Actor in Requests
Requests vulnerable to .netrc credentials leak via malicious URLs
Requests `Session` object does not verify requests after making first request with verify=False
Exposure of Sensitive Information to an Unauthorized Actor in Requests
Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function
Unintended leak of Proxy-Authorization header in requests
Python Requests Session Fixation
Insufficiently Protected Credentials in Requests
Requests (aka python-requests) before 2.3.0 allows remote servers to obtain a netrc password by reading the Authorization header in a redirected request.
Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header in a redirected request.
The resolve_redirects function in sessions.py in requests 2.1.0 through 2.5.3 allows remote attackers to conduct session fixation attacks via a cookie without a host value in a redirect.
The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to dis
Requests is a HTTP library. Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use `re
Requests vulnerable to .netrc credentials leak via malicious URLs
Requests `Session` object does not verify requests after making first request with verify=False
Requests is a HTTP library. Prior to version 2.33.0, the `requests.utils.extract_zipped_paths()` utility function uses a predictable filename when extracting files from zip archives into the system te
Key facts
- Latest version
- v2.34.2
- Last release
- 14 May 2026 (75 days ago)
- Total releases
- 158
- First release
- 14 February 2011
- Package age
- 15.5 years
- Maintainers
- not exposed by PyPI
- Known advisories
- 16
- Confidence
- High
Frequently asked
Is requests still maintained?
Yes — requests released as recently as 14 May 2026 (75 days ago), so it is actively maintained.
Does requests have known security vulnerabilities?
Yes — OSV lists 16 advisories for requests. See the advisory list on this page for the OSV/GHSA identifiers.
Is requests safe to use?
Maintained, but watch it — requests has real signals (drift, thin maintenance, or advisories) worth tracking. OSPulse rates it 55/100 (medium risk) based on release recency, cadence and known vulnerabilities.
Alternatives to requests
Other PyPI packages we've checked
requests is one package. What about the other hundreds in your tree?
Paste your own requirements.txt 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 PyPI registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.