The package has clear documentation, tests, an MIT license, and organization backing. Its small maintainer base, no commits in the last three months, absent security policy, and install-time script leave meaningful maintenance and review concerns.
65%
Total Score
67
100
88
50
A post-autoload-dump install-time script runs during Composer installation. The signal does not show what it does, but any install-time execution adds review and supply-chain exposure.
Only one registry account has publish access, which creates a thin publishing base. The organization backing shown by project_backing partly offsets that concern, but does not remove single-account dependency risk.
The package has existed for about 3 years and 11 months with eight releases, but only one release in the last 12 months. That indicates an established project with a relatively slow recent cadence.
The repository recorded zero commits and zero active maintainers in the last three months. Although the latest release was published recently, this weakens evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and review gap, though it is not evidence of a defect by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^10.0|^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.