Documentation, tests, licensing, and a matching repository provide useful transparency. A single registry maintainer and no security scanning reduce confidence in future fixes, while the package remains straightforward to inspect and has no install-time scripts.
58%
Total Score
50
86
75
Only one registry account has publish access. The linked repository is user-owned rather than organization-backed, so the narrow publishing base provides limited resilience if the maintainer becomes unavailable.
The package has had no releases in the last 12 months, and its latest release was about four years ago. That is a meaningful maintenance concern despite 13 total releases since 2020.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since its last push. This raises abandonment risk for a library dependency.
Composer build tooling is present, but no security-scanning tools were detected. The missing automated security coverage modestly lowers confidence in ongoing maintenance.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. 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/support Version ^6.0|^7.0|^8.0|^9.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.