The repository is still available and the package has a README, license, and release notes. Its single-maintainer ownership, no recent commits, and absent security policy leave maintenance capacity uncertain.
52%
Total Score
33
100
81
75
The latest release was published over nine years ago, with no releases in the last 12 months and only three releases overall. This is the strongest sign that the dependency may be effectively dormant.
There were zero commits and zero active maintainers in the last three months. Combined with the old registry release, this points to weak current maintenance capacity.
The repository is owned by the same individual namespace as the package rather than an organization. That is consistent ownership, but it offers less visible backing for long-term maintenance.
There were no new or closed issues or pull requests in the last month, and no open items. This is consistent with a quiet project but provides little evidence of ongoing support.
The repository uses Composer, but no security-scanning tools were detected. The build setup is present; the missing scanning is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
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.