The MIT declaration, focused file tree, and README make the package’s purpose and contents clear. It has no install-time scripts and is not deprecated or archived, but its single-maintainer ownership and absent security tooling reduce confidence in long-term support.
45%
Total Score
25
79
88
The package has had no release in over four years and none in the last 12 months. Its 16-release history shows earlier activity but does not compensate for the prolonged current gap.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating a strong abandonment concern.
One registry maintainer is a thin ownership base for a user-owned project, leaving limited visible support capacity if that account becomes inactive.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap rather than evidence that the package is unsafe.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
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.