Documentation, tests, and a matching source repository provide useful transparency. The small release history and absent recent commit activity leave maintenance uncertain, while organization backing and a clear license help offset that risk.
58%
Total Score
75
79
83
The package has only 3 releases since May 2023, with no releases in the last 12 months and an 18-month gap since version 0.2.0. This materially raises maintenance uncertainty.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The repository is not archived, but this recent inactivity still weakens confidence in ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning coverage is a modest maintenance-hygiene concern.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is not by itself evidence that the package is unsafe.
Version 0.2.0 is not a stable major release, so compatibility expectations are weaker even though it is not marked as a prerelease.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^7.0|^8.0|^9.0 | — | — |
league/flysystem Version ^3.0 | — | — |
illuminate/console Version ^7.0|^8.0|^9.0 | — | — |
illuminate/routing Version ^7.0|^8.0|^9.0 | — | — |
illuminate/support Version ^7.0|^8.0|^9.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.