leafs/http

Healthy and reasonable to adopt, with a small maintenance risk. It has regular releases, active recent commits, tests, and organization backing, but all recent commits come from one contributor and repository security hygiene is limited.

Latest v5.0.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 12 commits in the last 3 months, creating a narrow individual bus factor. Organization ownership provides some ability to transfer maintenance, but no second active contributor is shown.

Repo issue activity

There are only 2 open issues, no open pull requests, and no issues or pull requests were opened or closed in the last month. The low activity is a modest concern, though the small project size and recent commits provide some compensation.

Repo popularity

The repository has 6 stars, 12 forks, and 1 watcher. Low popularity limits community validation, but popularity is supporting evidence and does not outweigh the active release and commit history.

Repo tooling

Composer build tooling is present, but no security-scanning tools are detected. Build support is appropriate for this PHP package; the missing scanning layer is a transparency and maintenance gap.

Security policy

The repository has no security policy. That makes vulnerability reporting and coordinated fixes less explicit, although the README provides an informal contact path.