slepic/http-transfer

Clear documentation, tests, licensing, and a recent release make the package straightforward to evaluate. Its small release history, single maintainer, and lack of security policy leave less evidence of sustained maintenance.

Latest 1.0.1

Packagist

68%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed. Because the repository is user-owned rather than organization-backed, this leaves limited visible publishing redundancy.

Project backing

The registry namespace and repository owner match, but ownership is an individual account rather than an organization. This supports identity consistency while offering limited evidence of broader project backing.

Release history

The package has four releases over about seven years, with a median interval of about 787 days, although one release occurred in the last 12 months. This supports continued availability but suggests an infrequent maintenance cadence.

Repo commit activity

There were no commits and no active maintainers in the last three months. The recent release provides some compensating evidence, but the current lack of development activity weakens confidence in ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.