php http client
65%
Total Score
50
100
83
90
Only one account has registry publish access. That is a narrow publishing base for a user-owned project and increases continuity risk, though repository activity provides some compensating evidence.
A substantive README documents the HTTP client API, but neither the artifact nor repository contains tests or a changelog. For a network-facing client, the absence of visible tests reduces maintenance transparency.
The repository is owned by a user account rather than an organization, so there is no organizational backing to offset the narrow maintainer base.
The repository records 0 commits and 0 active maintainers in the last 3 months. Although the latest release and repository push are recent, the lack of sustained commit activity is a meaningful maintenance concern.
There are no open issues or pull requests and no issue or PR activity in the last month. This is not inherently negative, but it provides no evidence of an active maintenance or review community.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.