Standards-compliant APIs in Laravel, one RFC at a time.
60%
Total Score
caution
A brand-new 0.x release has no established maintenance record, and all workflow actions are unpinned.
Only one registry account has publish access. This is a meaningful bus-factor concern for a user-owned project, though repository activity is too new to establish whether additional contributors will emerge.
This is a newly published package with two releases over less than two hours and no longer maintenance record. The rapid initial releases are not inherently negative, but support continuity is unproven.
There were no commits or active maintainers in the measured three-month window. Because the repository is only hours old, this primarily shows that maintenance history is unproven rather than established abandonment.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest repository hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, although it does not by itself indicate poor code maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^13.30 | — | — |
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.