p3k/http

The MIT license, clear README, and small dependency set make the package easy to evaluate and adopt. The repository is not archived, but it has had no commits or releases for nearly two years and lacks a security policy.

Latest 0.1.13

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 14 releases since April 2017, but none in the last 12 months; the latest release was nearly two years ago. That indicates materially reduced maintenance activity.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old latest release, this is the strongest evidence that active maintenance has slowed or stopped.

Repo issue activity

There are no new issues or pull requests in the last month, and two pull requests remain open. This is consistent with a quiet project and adds modest maintenance uncertainty.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling is present. The missing scanner is a hygiene gap, not evidence that the package is unsafe by itself.

Security policy

The repository has no security policy. For a network-facing HTTP client, this reduces transparency about vulnerability reporting and response expectations.