The README and release notes provide basic consumer context, and the repository identity matches the package. The two-file artifact and absent security policy leave little transparency for a long-lived dependency.
38%
Total Score
0
63
50
This package has only one release, published in June 2017, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push in June 2017 and materially increasing abandonment risk.
No license is declared, and no license file was found in either the package or repository. This creates a direct adoption and redistribution concern.
The published artifact contains only README.md and composer.json, leaving little implementation or documentation surface to assess. This may fit a minimal test hook, but provides limited transparency for a dependency.
The repository has no security policy. For a small, inactive project this reduces clarity about vulnerability reporting and maintenance expectations.
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.