The README, tests, MIT license, and small dependency set make integration clear. The project also lacks a security policy and has one unpinned workflow action, adding modest transparency and build-hygiene concerns.
38%
Total Score
50
100
75
83
The package and repository are owned by the same individual account. This confirms ownership alignment but provides no organizational maintenance cushion.
The package has had no release in about two years and four months, with five releases overall and none in the last 12 months. That is strong evidence of stalled maintenance for a framework integration package.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push and stale release history, this materially increases abandonment risk.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little external evidence of adoption or community support.
Composer build tooling is present, but no security scanning tools were detected. This is a modest supply-chain hygiene gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^11 | — | — |
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.