The MIT license, repository tests, and stable release format make the package easier to evaluate. Its tiny, inactive project footprint and lack of security tooling leave adoption exposed to abandonment risk.
38%
Total Score
0
67
50
The latest release was about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite a long history of 19 releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly 10-year release gap.
The repository has zero stars and forks and only one watcher, providing little evidence of an active user or contributor community. Popularity is supporting evidence, but this reinforces the maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This modestly reduces confidence in ongoing maintenance practices.
No security policy was found, leaving vulnerability-reporting expectations and response procedures unclear. This is a transparency and maintenance gap, not evidence of malicious behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ~5.0 | — | — |
illuminate/console Version ~5.0 | — | — |
illuminate/support Version ~5.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.