Niquests
Shares rank 6 of 11 HTTP client libraries by recommenders
Drop-in replacement for requests that adds HTTP/3, async and multiplexing while keeping the familiar API. Critics raise trust concerns and note it is largely a one-man project.
Drop-in replacement for requests that adds HTTP/3, async and multiplexing while keeping the familiar API. Critics raise trust concerns and note it is largely a one-man project.
11 people gave an opinion
- recommend it
- 8
- criticize it
- 3
- approval share
- 73%
Recommended in 4 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 8 people recommend itNeeds 10 or more, not met.
- 2.7 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Drop-in replacement for requests
“It is a drop-in replacement for the Python requests library that focuses on bringing modern HTTP features to the familiar API we all know.”
Comment from 21 Jan 2026 in “Show HN: Safest, Fastest, Easiest, and Most Advanced Python HTTP Client” “The switch was surprisingly smooth. I think there's an official migration guide in the doc.”
Comment from 25 Mar 2026 in “I Forked Httpx” “which is a dropin replacement and imo wayyy better than httpx”
Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python” - Comment from 7 Apr 2026 in “Show HN: Niquests – A Requests fork, three years of catching Python's HTTP up”
- Comment from 25 Mar 2026 in “I Forked Httpx”
Modern HTTP features like HTTP/3 and multiplexing
“I wanted the beautiful, ergonomic API of requests, but I wanted it to speak the modern web and solve most seen struggles around HTTP consumption.”
Comment from 13 Mar 2026 in “Show HN: I forked Python's Requests to add HTTP/3, async, and multiplexing” “It is a drop-in replacement for the Python requests library that focuses on bringing modern HTTP features to the familiar API we all know.”
Comment from 21 Jan 2026 in “Show HN: Safest, Fastest, Easiest, and Most Advanced Python HTTP Client” “multiplexing story in httpx is quite limited compared to what niquests offers out of the box”
Comment from 25 Mar 2026 in “I Forked Httpx” - Comment from 25 Mar 2026 in “I Forked Httpx”
Seen as better than httpx
“We have switched to niquests in my company and yes I can confirm that it's 10x better than httpx”
Comment from 25 Mar 2026 in “I Forked Httpx” “which is a dropin replacement and imo wayyy better than httpx”
Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python” “I feel like it has always been such a better package”
Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python” Stable and actively developed
“actively developed, supports all the things I mentioned above”
Comment from 29 Aug 2026 in “Migrating to HTTPX2” “Very stable actually. We've enabled it by default as such.”
Comment from 7 Apr 2026 in “Show HN: Niquests – A Requests fork, three years of catching Python's HTTP up” “the experience has been good”
Comment from 28 Aug 2026 in “Migrating to HTTPX2”
What people warn about
Each mark is one comment
Trust and single-maintainer concerns
“I opened an issue some time ago about them monkey patching urllib3, it was fixed than but I now see the issue has been outright deleted.”
Comment from 28 Aug 2026 in “Migrating to HTTPX2” “the sponsorship subscription thing in the readme gives me vague rugpull vibes”
Comment from 25 Mar 2026 in “I Forked Httpx” “niquest is something like a one-man-show, which is an issue-per-se”
Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python”
Other HTTP client libraries people recommend
The four most recommended other HTTP client libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Requests (Python library) | 23 | 7 | 77% | 8 | — | Approved |
| Axios | 21 | 37 | 36% | 5 | — | — |
| Go net/http | 12 | 7 | 63% | 4 | — | — |
| libcurl | 10 | 2 | 83% | 7 | — | Approved |
| NiquestsThis page | 8 | 3 | 73% | 4 | — | — |
What people said
All 20 comments that mention it, newest first. Each links to the original comment.
“actively developed, supports all the things I mentioned above”
“niquest is something like a one-man-show, which is an issue-per-se”
“I feel like it has always been such a better package”
“which is a dropin replacement and imo wayyy better than httpx”
“the experience has been good”
“I opened an issue some time ago about them monkey patching urllib3, it was fixed than but I now see the issue has been outright deleted.”
“Very stable actually. We've enabled it by default as such.”
“we've exposed better way to achieve that (e.g. mTLS in memory, network fine tuning, peer cert retrieval, ...)”
“The drop-in compatibility story is what makes this viable”
“The switch was surprisingly smooth. I think there's an official migration guide in the doc.”
“multiplexing story in httpx is quite limited compared to what niquests offers out of the box”
“We have switched to niquests in my company and yes I can confirm that it's 10x better than httpx”
“the sponsorship subscription thing in the readme gives me vague rugpull vibes”
“It is indeed a shame that niquests isn't used more”
“niquests easily beat aiohttp just using 10 conn”
“more features, a breeze to switch”
“instead of forking join forces... See Niquests”
“we managed to get almost every plugin/3rd party tool bound to Requests in a working condition with this fork.”
“I wanted the beautiful, ergonomic API of requests, but I wanted it to speak the modern web and solve most seen struggles around HTTP consumption.”
“It is a drop-in replacement for the Python requests library that focuses on bringing modern HTTP features to the familiar API we all know.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.