A single maintainer and no commits in the last three months limit ongoing support. The package is well documented, tested, licensed, and not deprecated or archived, which offsets some maintenance risk.
58%
Total Score
50
100
83
75
The registry lists one maintainer. That is a limited publishing base and increases continuity risk for a package with already sparse release activity.
The repository is owned by an individual user rather than an organization. Combined with one registry maintainer, this indicates limited visible project backing.
The package has only two releases across about 22 months, with no releases in the last 12 months and a median interval of about 285 days. This indicates a thin release history and raises maintenance concerns.
The repository recorded zero commits and zero active maintainers in the last three months. This is direct evidence that current maintenance has paused.
There is one open issue and no issue or pull-request activity in the last month. This is a weak maintenance signal, though the small project size makes the absence of activity inconclusive by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-http/httplug Version ^2.0 | — | — |
php-http/discovery Version ^1.0 | — | — |
php-http/message-factory Version ^1.0 | — | — |
php-http/client-implementation Version ^2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.