The package is well documented, licensed, and backed by a substantial source tree with repository tests. Workflow references are all unpinned, and the repository has no security policy or scanning, leaving avoidable maintenance and build-integrity gaps.
58%
Total Score
50
100
83
75
Only one registry account has publish access. The linked repository is owned by the same individual rather than an organization, so there is no provided backing signal to offset the single-maintainer continuity risk.
The registry namespace and repository are owned by the same individual account, with no organization backing shown. This is consistent ownership but offers limited continuity evidence.
The package has 10 releases in 159 days, but all were published by April 19, 2026; the median interval was about 20 hours, followed by roughly five months without a release. This suggests an early burst of activity with uncertain continuation.
There were zero commits and zero active maintainers in the last three months. For a package only about five months past its latest release, this is a meaningful warning about ongoing maintenance.
The repository has 2 stars, 0 forks, and 0 watchers. Low adoption is only supporting evidence, but it provides little external validation for a young package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/bus Version ^11.0|^12.0|^13.0 | — | — |
illuminate/queue Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.