drewlabs/http-query

This release appears usable and reasonably transparent, with an MIT license, a linked non-archived organization-owned repository, recent release and commit activity, a documented README, repository tests, and no install-time lifecycle scripts. The main concerns are its pre-1.0 maturity, modest release history, only two commits in the last three months from one contributor, no repository security policy or security-scanning tooling, and no workflow automation; the organization backing partly mitigates the concentrated contributor base. Overall, it is a viable dependency with maintenance and security-hygiene caveats rather than a clear abandonment risk.

Latest v0.4.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 2 recent commits came from one contributor, creating a concentrated bus factor. Because the repository is organization-owned, maintenance handoff is more plausible than for an unaffiliated single-maintainer project, but the observed activity remains narrow.

Repo commit activity

The repository recorded 2 commits in the last 3 months, so maintenance is present but light rather than vigorous.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no pull requests were open. This provides little evidence of an active external maintenance community.

Repo popularity

The repository has zero stars, forks, and watchers, indicating limited external adoption or visibility. Popularity is supporting evidence only, so this is a modest concern rather than a decisive health problem.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing security automation is a hygiene gap for a package that handles HTTP requests.