simsoft/http-client

This release appears healthy and reasonably safe to depend on: it has a stable major version, frequent recent releases, an active and non-archived repository, current commit and pull-request activity, a matching repository with clear package references, a permissive MIT license, documented security reporting, and restrictive workflow permissions. The main limitations are the very small visible maintainer and contributor base, zero repository popularity, and the absence of automated security-scanning tooling; these create some continuity and assurance concerns but are partly offset by two active contributors, 32 commits in the last 3 months, 21 merged pull requests in the last month, and substantial repository documentation and tests.

Latest 5.0.0

Packagist

86%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publish access, which creates a publishing continuity concern for an independently owned project. Repository activity from two contributors provides some compensation, but does not eliminate the single-publisher risk.

Project backing

The repository is owned by the sim-soft user account rather than an organization, so there is no organizational maintenance cushion to offset the small maintainer base. Active repository and release signals nevertheless show current individual backing.

Repo popularity

The repository has zero stars, forks, and watchers, which limits community validation and external adoption evidence. Popularity is supporting evidence rather than decisive, and the active release and commit signals compensate for much of this gap.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning layer is a genuine assurance gap, although the repository does provide a security policy and controlled CI permissions.