imroc/req

Simple Go HTTP client with Black Magic

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 14th, 2026
Created on February 25th, 2017
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 409
Total Stargazers: 4,862 (+0)
Total Subscribers: 63 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.8 hours
Mean response time: 110.6 days
90th percentile: 516.0 days
Tracked items: 136

Most active contributors

Sign in to see contributor activity.

How this project is maintained

55% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 554 days
Stale 30+ days: 15
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • priority:low (29)
  • enhancement (24)
  • bug (14)
  • modified-stdlib (13)
  • question (12)
  • priority:medium (9)
  • quic-go (8)
  • priority:high (5)

Detailed Description

req is a Go HTTP client library that simplifies making HTTP requests with a fluent, chainable API.

The tool addresses the verbosity and complexity of Go's standard net/http package by providing a higher-level interface that reduces boilerplate code. It uses method chaining to build requests progressively, allowing developers to set headers, query parameters, request bodies, and other options in a readable sequence. The library handles common patterns like automatic JSON marshaling and unmarshaling, making it faster to write typical HTTP client code compared to working directly with the standard library.

Developers should choose this tool if they frequently make HTTP requests and want cleaner, more concise code than the standard library provides. It suits projects where readability and developer velocity matter more than minimal dependencies. The tool is particularly valuable for building API clients, microservices, and applications that make many external HTTP calls. It works well in contexts where the standard library's verbosity becomes a friction point but a full-featured HTTP framework is unnecessary.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase receives consistent attention to code quality and testing practices. The maintainers respond to issues and incorporate community feedback into releases.