RepoRadarSide by side
psf/requests vs encode/httpx
- psf/requests
Healthy
Maintained by 1 person in the last 90 days, no known risks.
- encode/httpx
Healthy
No known risks in the checks that ran.
| Fact | psf/ | encode/ |
|---|---|---|
| Maintenance | ||
| Status | Slowing | Steady |
| Human commits, 90 days | 1 | 0 |
| Last human commit | Aug 25, 2026 (2 months ago) | Feb 23, 2026 (8 months ago) |
| Last release | May 14, 2026 (6 months ago) | Dec 6, 2024 (1 year ago) |
| Median PR merge time | 2 hours | 12 hours |
| Issues with a maintainer reply | 42% of 26 | Too few to measure |
| People | ||
| Authors, 90 days | 1 | 0 |
| Authors for half of commits | 1 | 2 |
| Owner | Organization | Organization |
| Stars | ||
| Stars | 54.7k | 15.8k |
| Star history | Organic, confidence high | Organic, confidence medium |
| Risk | ||
| Risk flags | None | None |
| License | Apache-2.0 | BSD-3-Clause |
| Advisories, latest version | None listed | No packages found |
| OpenSSF Scorecard | 8.2 / 10 | 4.9 / 10 |
| Archived | No | No |
| Named successor | None | None |
Each verdict comes from the same published rules. RepoRadar doesn't pick a winner: which facts matter depends on how you'll use the code. Open either report for the evidence behind each number.
Package and advisory data: deps.dev and OSV.