Clear licensing and a usable README make the package easy to evaluate, while its small dependency footprint and organizational backing reduce adoption friction. The lack of a security policy leaves limited guidance if problems arise.
45%
Total Score
50
100
75
50
The latest release was published about six years and eight months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite seven total releases.
The repository recorded no commits and no active maintainers during the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.
Composer is used as a build tool, but no security-scanning tooling is present. This is a modest supply-chain hygiene gap in an otherwise small project.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though not as serious as the maintenance lapse.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer 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.