Tests, a clear README, and an MIT license make the package transparent to integrate. Its small dependency set and package-to-repository match help, but limited security tooling and issue activity weaken confidence in ongoing support.
40%
Total Score
33
100
71
83
The latest release was published about nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being deprecated.
There were no commits and no active maintainers in the last three months, consistent with the last repository push being about eight years ago. This materially increases maintenance and abandonment risk.
The registry namespace and repository are owned by the same individual, so the package has a consistent owner but no organizational backing shown by this signal.
There has been no issue or pull-request activity in the last month, with two open issues remaining. This is a modest sign that current support may be limited.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, though it is secondary to the package's long inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version * | — | — |
illuminate/validation Version * | — | — |
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.