Consumer transparency is weak, and the project has no security policy. The linked repository is correctly identified, but the available maintenance evidence is too old for a dependable new dependency.
34%
Total Score
50
61
63
The package and repository each contain only composer.json, leaving no visible implementation, documentation, or supporting project files. That extremely thin tree makes the release difficult to evaluate and maintain.
The package has made no release in about 10 years, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency expected to receive maintenance.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being about 10 years ago. This materially increases abandonment risk.
No declared license or license file was found in the package or repository. This creates a genuine adoption and redistribution concern.
The package has no README, tests, or changelog. Missing tests and changelog are normal for a published artifact, but the missing README weakens consumer transparency.
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.