The MIT license, substantial README, tests, and release notes improve transparency. The small user-owned project has no security scanning, leaving limited independent evidence of ongoing project capacity.
57%
Total Score
50
100
81
75
The package has only two releases, both clustered within about four hours, and no releases in the last 12 months despite being about 16 months old. This weakens confidence in sustained maintenance.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since the latest release and raising abandonment concerns.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, so there is no documented path for reporting vulnerabilities or explaining security practices. This adds a minor transparency concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^8.0|^9.0|^10.0|^11.0 | — | — |
illuminate/support Version ^8.0|^9.0|^10.0|^11.0 | — | — |
illuminate/database Version ^8.0|^9.0|^10.0|^11.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.