Usable with caveats: the release is clearly packaged, licensed, tested, and backed by the matching source repository, but it has seen no release or commit activity for nearly six years. Its 0.x status and lack of security policy make it a weaker choice for a new dependency than an actively maintained alternative.
55%
Total Score
25
100
72
88
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing that maintenance has effectively stopped rather than merely slowed.
The registry namespace and repository owner match, providing consistent ownership evidence; the owner is an individual account rather than an organization, so there is limited visible institutional backing.
Only two releases exist, with the latest published in September 2020 and no releases in the last 12 months; this long period without updates raises abandonment and compatibility risk.
The repository has no stars and only one fork and watcher, offering little community evidence to compensate for the long maintenance gap.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency gap, especially for an inactive package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 6.3.*|7.* | — | — |
illuminate/support Version 5.*|^6.0|^7.0|8.* | — | — |
illuminate/container Version 5.*|^6.0|^7.0|8.* | — | — |
illuminate/validation Version 5.*|^6.0|^7.0|8.* | — | — |
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.