The README is thorough, the MIT terms are clear, and installation has no lifecycle scripts. Solo ownership, no tests, and no security policy leave limited evidence for long-term support.
58%
Total Score
50
86
75
One registry maintainer creates a thin support base, and the linked repository is user-owned rather than organization-backed. This increases continuity risk if that maintainer becomes unavailable.
This is the only release, published about two years ago, with no releases in the last 12 months. That is meaningful evidence of limited ongoing maintenance for a library.
The repository had no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no recent activity showing continued care.
Composer build tooling is present, but no security scanning tools were detected. The tooling supports normal package construction while offering limited security-process evidence.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This is a transparency gap, though it is not evidence that the package is unsafe.
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.