The stable MIT-licensed release has a clear, small source tree and no install-time scripts. Maintenance appears stopped, and the single-person project has no security policy.
42%
Total Score
25
67
88
The package has had no release in more than three years and none in the last 12 months, despite nine releases overall. Its earlier release cadence shows prior activity but does not offset the prolonged gap.
There were no commits and no active maintainers in the measured three-month period, consistent with maintenance having stopped for a prolonged period.
Only one registry publishing maintainer is listed. Individual ownership is not inherently unhealthy, but it leaves limited visible publishing redundancy alongside the inactive project.
The repository name matches the package, but its README does not mention the package name directly. That creates a modest ownership and packaging-transparency concern.
Composer is used for the build, providing expected ecosystem tooling, but no security scanning tools were detected. The missing scanner is a modest transparency gap rather than proof of unsafe code.
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.