Frequent releases and recent updates help, but all recent commits come from one contributor. The short README and absent security policy leave limited guidance for integrating or reporting problems.
64%
Total Score
50
100
86
75
One contributor made all 2 recent commits, giving the project a 100% top-contributor share. This leaves maintenance dependent on a single active individual.
The repository recorded only 2 commits in the last 3 months. Recent activity exists, but the low volume provides limited evidence of sustained maintenance capacity alongside the rapid release cadence.
The repository name does not match the package name and its README does not mention the package. A name mismatch can be normal for a sub-package, but the lack of any README reference makes the package-to-source relationship unclear.
Composer is used for builds, but no security-scanning tool was detected. For a Laravel administration package, this weakens the project's visible security hygiene.
The repository has no security policy. That leaves no documented channel or process for reporting vulnerabilities, which reduces transparency for a package used in application administration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ~11|~12|~13 | — | — |
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.