The MIT license, focused eight-file layout, and clear README keep adoption straightforward. Its single maintainer and lack of security scanning leave little support if Laravel compatibility breaks.
38%
Total Score
25
79
50
The package has had only two releases, both published in May 2018, and none in the last 12 months. This strongly indicates abandonment risk despite the package not being deprecated.
The repository recorded no commits and no active maintainers in the last three months, consistent with its last push in May 2018. There is no observed maintenance capacity for compatibility or bug fixes.
Only one registry maintainer is listed, leaving the package dependent on a single publisher. The linked repository is also owned by an individual rather than an organization, so no broader backing is shown.
Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate for the package, while the missing security checks are a modest transparency gap.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This compounds the risk of relying on a project 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.