The package has almost no published implementation or consumer documentation, and its only release was over seven years ago. The repository has no recent commits, tests, changelog, or security policy, leaving maintenance and support uncertain.
28%
Total Score
25
100
63
50
Both the package and repository contain only composer.json, with no implementation files or documentation visible in the collected tree. That makes the release difficult to inspect and materially weakens transparency.
There has been only one release, published over seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in 2019. No compensating maintenance activity is shown.
The package has no README, while the repository also has no tests or changelog. Missing tests and changelog are normal for published artifacts, but the absent README is a real consumer-documentation gap for a library.
The repository is owned by an individual user rather than an organization, and no organizational backing is shown. Combined with the inactive history, this leaves limited visible maintenance capacity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.