The tiny seven-file artifact has no runtime dependencies and avoids install scripts, which limits moving parts. It also lacks a security policy and automated security scanning, leaving little visible support for long-term maintenance.
44%
Total Score
25
100
56
83
Neither the package nor the linked repository declares or contains a detectable license. This creates a real legal and adoption risk for developers considering the dependency.
The package has only one release, published about 22 months ago, with no releases in the last 12 months. That leaves compatibility and ongoing maintenance largely unproven.
There were no commits and no active maintainers in the three months measured. Combined with the single-release history, this is a substantial abandonment concern.
The package has no README, while tests and a changelog are normally repository concerns and their absence is not itself a packaging gap. Missing consumer documentation is still a concern for a Laravel integration package.
The package and repository are owned by the same individual account, so the source association is clear, but there is no organization backing shown to compensate for the thin maintenance evidence.
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.