The package has clear documentation, tests, licensing, and a small dependency surface. Single-person ownership and no security policy reduce resilience if maintenance stops.
65%
Total Score
50
100
86
83
The registry lists one maintainer. That is consistent with a small personal project, but it leaves little visible maintenance capacity if that person becomes unavailable.
The registry namespace and repository are owned by the same individual account, so ownership is consistent. It does not provide organizational backing to compensate for the thin maintainer base.
Four releases were published within the first day, then none followed during the package's roughly five-and-a-half-month lifetime. This suggests an unfinished or inactive release cycle despite the initial burst of activity.
There were no commits and no active maintainers in the last three months. For a package that has already been released, this is meaningful evidence of stalled maintenance.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanner is a modest transparency and maintenance gap, not a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-client Version ^1.0 | — | — |
psr/http-factory Version ^1.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.