The package has tests, a README, an MIT license, and a small dependency surface. However, its last release and repository activity were nearly ten years ago, with no security policy or scanning.
58%
Total Score
25
100
72
75
The latest of only three releases was published nearly ten years ago, with no releases in the last 12 months and a median interval of about 543 days. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. This materially lowers confidence in ongoing maintenance.
The repository is owned by an individual user rather than an organization, so the single registry maintainer offers little evidence of organizational continuity. This reinforces the maintenance concern but does not independently establish abandonment.
The repository has only 4 stars, 3 forks, and 2 watchers, indicating limited adoption and a thin external support signal. Popularity is supporting evidence, so this is a modest concern rather than a standalone blocker.
The project uses Composer, but no security scanning tools were detected. That is a hygiene gap for dependency maintenance and vulnerability visibility.
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.