The MIT license and matching repository make its ownership and reuse terms clear. Its single-maintainer footprint leaves little visible support if integration problems arise.
38%
Total Score
25
75
50
Only one release was published, with no releases in the last 12 months; the package has had no new version for about 9 years and 11 months. This is strong evidence of abandonment risk for a Laravel integration package.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history showing no updates for about 9 years and 11 months.
One registry maintainer is enough for a small package, but there is no broader publishing base visible to provide continuity if that maintainer stops supporting it.
Composer is used, which fits the package ecosystem, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence of a direct defect.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a package that exposes Laravel controllers and routes.
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.