php-fig/http-client
None observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3240
- days_rel: n/a
- days_push: 1075
- n_releases_24m: 0
Adoption not part of the score
1721 stars · 17 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The official PHP-FIG repository holding the PSR-18 HTTP Client specification interfaces. It provides only abstractions (interfaces), not an actual HTTP client implementation.
Use cases
- decouple my code from a specific http client library
- build an http client that conforms to psr-18
- type-hint against a standard http client interface in php
- find psr-18 compliant http client implementations
- write library code that works with any psr-18 http client
When to choose
- you are writing a reusable PHP library that needs to send HTTP requests without depending on a specific client
- you are implementing a PSR-18 compliant HTTP client
- you want interoperability with the PHP-FIG ecosystem
When to avoid
- you need an actual working HTTP client to make requests (use Guzzle, Symfony HttpClient, or another PSR-18 implementation)
- your project does not follow PSR standards
Facets
library · maturity stable
http-client sdk web-development apis developer-tools php psr-18 interfaces standards abstraction
1 source
- readme: https://github.com/php-fig/http-client · fetched 2026-08-28 · 2864b8d92262
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| php-fig/http-client | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="php-fig/http-client")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem