The package includes extensive tests, a changelog, release notes, a matching repository, and an MIT license. Its workflows use broad or unpinned references, and the repository has no security policy, leaving maintenance and build-hygiene concerns.
62%
Total Score
50
88
83
The repository is owned by an individual rather than an organization, so the single registry maintainer represents a genuinely thin ownership base. This increases continuity risk if that maintainer stops work.
Only two releases were published, with the latest about 13 months ago and no releases in the last 12 months. The initial one-week release interval shows a short launch period but does not compensate for the prolonged later silence.
The repository recorded zero commits and zero active maintainers over the last three months. Combined with the long release gap, this is meaningful evidence that development may have stalled.
Composer build tooling is present, but no security-scanning tools were detected. For a library distributed through a package registry, that is a modest build and review gap.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0 | — | — |
illuminate/console Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
illuminate/database Version ^11.0|^12.0 | — | — |
illuminate/contracts Version ^11.0|^12.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.