Tests, a usable README, and a license provide solid project basics. The project lacks a security policy and has a single registry maintainer, so ongoing support deserves attention.
67%
Total Score
50
100
94
83
Only one account has registry publish access. That is a limited publishing base for a user-owned project and increases continuity risk if the maintainer becomes unavailable.
The repository recorded zero commits and zero active maintainers in the last three months. Although releases occurred within the last year, the short-term lack of development activity is a maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
No repository security policy was found, leaving reporting and response expectations undocumented for a framework integration package.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all three referenced actions are unpinned, which weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/routing Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-fractal Version ^6.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.