The lone maintainer, five runtime dependencies, and no security scanning or policy leave limited visible resilience. MIT licensing, a matching repository, and release notes provide useful transparency, but not enough to offset the maintenance risk.
45%
Total Score
25
50
75
75
This package has only one release, published about 2 years and 7 months ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package having received no recent development attention.
Five runtime dependencies, including Guzzle and several Illuminate components, increase the package's maintenance and compatibility surface. No compensating development dependencies or testing signal were provided.
One registry maintainer creates a thin publishing base and increases continuity risk, although the linked repository is owned by the same individual.
Composer is used for builds, but no security-scanning tool is configured. The missing scanner modestly reduces assurance for a package with several runtime dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^8|^9|10.x-dev | — | — |
guzzlehttp/guzzle Version * | — | — |
illuminate/console Version ^8|^9|10.x-dev | — | — |
illuminate/support Version ^8|^9|10.x-dev | — | — |
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.