Tests, a README, and release notes provide a workable starting point. The package is directly tied to its repository and has no install-time scripts, but its longer-term maintenance capacity remains unproven.
68%
Total Score
50
100
88
75
Only one registry maintainer is listed. That is manageable for a new personal project but leaves limited visible publishing redundancy if the maintainer becomes inactive.
The registry namespace and repository are owned by the same individual account, which supports ownership alignment but provides no organizational backing or redundancy.
The package is only 0 days old, with three releases published over roughly one day; this shows active initial publishing but provides no meaningful long-term maintenance history.
There were no commits or active maintainers during the prior three months, but the repository was only 0 days old and had been pushed minutes earlier, so this is mainly an unproven-history concern rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected. For a newly published dependency, that is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/redis Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.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.