The repository has had no commits in three months, and releases are widely spaced. A recent release with notes, tests, a clear license, and a focused dependency set provides useful supporting evidence.
67%
Total Score
50
100
88
50
The package has only three releases over about 26 months, with one release in the last 12 months and a median interval of about 320 days. This indicates slow maintenance, though it is not abandonment by itself.
There were zero commits and zero active maintainers in the last three months. For a maintained library, that is a meaningful sign of slowed development and raises the risk that compatibility issues may linger.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of an unsafe release.
The repository has no security policy. That weakens the project's documented process for receiving and handling vulnerability reports.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all five action references are unpinned, leaving the build exposed to upstream action changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.5 | ^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.