The single-maintainer base and unpinned workflow actions weaken long-term confidence. A clear MIT license, documentation, repository tests, and a small dependency set provide useful adoption support.
56%
Total Score
50
100
88
75
Only one registry maintainer is listed. With a user-owned project and no recent activity, this creates a thin continuity and bus-factor concern.
This package has made one release, with no releases in the last 12 months; the release is about 1 year and 6 months old. That leaves limited evidence of ongoing maintenance.
There were no commits and no active maintainers in the last 3 months. Combined with the single-release history, this is the strongest evidence of uncertain ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance-hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^10.0|^11.0|^12.0 | — | — |
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.