The README, tests, MIT licensing, and matching repository provide useful transparency. Its single-person ownership and lack of recent commits leave future fixes uncertain.
60%
Total Score
50
100
88
75
Only one registry maintainer is listed. That is consistent with an individually owned project, but it leaves limited visible publishing redundancy when combined with the absence of recent repository commits.
The package and repository are both associated with the same individual rather than an organization. This supports clear ownership but provides little evidence of broader project backing.
The package has 12 releases over 642 days, but only one release in the last 12 months. That sharply slower cadence raises maintenance uncertainty despite the recent latest release.
The repository recorded zero commits and zero active maintainers in the last three months. This is a concrete maintenance gap for a package that may need compatibility fixes as Laravel evolves.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a hygiene limitation rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^11.0|^12.0|^13.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.