Clear documentation, licensing, and release notes make adoption easier. The repository lacks a security policy and security scanning, limiting transparency and response readiness.
68%
Total Score
67
88
75
All four recent commits came from one contributor. Organizational ownership provides some handoff capacity, but no second active contributor is shown to reduce concentration risk.
Four commits were made in the last 3 months, so activity is present but not extensive. This supports ongoing maintenance without showing a broad or highly active development effort.
The project uses Composer, but no security-scanning tooling was detected. That leaves a meaningful repository hygiene gap for a network-facing client library.
No repository security policy was found, so the process for reporting and handling vulnerabilities is unclear.
Version 0.2.3 is not a stable-major release, so compatibility may still change. It is not a prerelease, which partly offsets that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
amphp/dns Version ^2.4 | — | — |
league/uri Version ^7.8 | — | — |
amphp/cache Version ^2.0 | — | — |
amphp/socket Version ^2.3 | — | — |
amphp/http-client Version ^5.3 | — | — |
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.