The single-maintainer project has no security policy or scanning, and its published license conflicts with the detected MIT file. The README documents basic Laravel integration.
42%
Total Score
25
60
50
The latest release was over 9 years ago, with no releases in the last 12 months. That strongly indicates abandonment for a framework integration package.
The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the release history and leaving current maintenance unverified.
The artifact contains an MIT license file, but the manifest declares the package proprietary. This mismatch creates avoidable legal uncertainty despite the presence of a license file.
Only one registry maintainer is listed, leaving a thin publishing base; the linked repository is user-owned rather than organization-backed, so there is little visible continuity support.
Composer is used as the build tool, but no security scanning tools are configured. This is a hygiene gap that adds risk for a package with no recent maintenance.
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.