The artifact has no README or tests, and the repository has no security policy or automated security scanning. Apache-2.0 licensing, a matching repository, and a recorded release note provide useful transparency, but not enough to offset the thin project evidence.
38%
Total Score
0
67
50
The package has had only three releases, all concentrated between April 29 and May 1, 2023, with no release in more than three years. This strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and limited evidence of ongoing maintenance.
The published artifact has no README or tests, while the repository also reports no tests or changelog. The GitHub release notes for this version provide some documentation, but consumer guidance and validation coverage remain thin.
Composer is used for the build, which is a positive baseline, but no security-scanning tools are configured. That weakens assurance given the package's inactivity.
The repository has no security policy, leaving no published process for reporting or handling security issues. This is a meaningful transparency gap for a server package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
amphp/http Version ^2.0 | — | — |
l3tum/php-uring Version ^0.1 | — | — |
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.