The package includes tests, a substantial README, release notes, and a matching MIT license. Its four releases arrived within about four hours, followed by roughly six months without commits, while the workflow uses two unpinned actions and the repository has no security policy.
58%
Total Score
50
100
83
67
The package and repository are owned by the same individual account, so ownership is coherent, but there is no organization backing shown to compensate for the single-person maintenance base.
All four releases were published on the same day, with a median interval of about 1 hour 19 minutes, and there has been no later release across roughly six months. This rapid launch followed by a long quiet period raises abandonment risk.
There were zero commits and zero active maintainers in the last three months, indicating that maintenance has currently stopped. The recent release history and complete package structure provide some compensation but do not remove the concern.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption signal to offset the thin maintenance history.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/bus Version ^10.0|^11.0|^12.0 | — | — |
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/queue Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.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.