The release includes useful notes and a clear README, but the project has no security policy and its only workflow action is unpinned. It is not deprecated or archived, and its small dependency set limits complexity.
58%
Total Score
50
86
75
The repository is owned by an individual user rather than an organization, so there is no visible organizational continuity to offset the single-maintainer and inactive-commit signals.
The package has six releases since April 2023, but none in the last 12 months; the latest release was about 19 months ago. This indicates materially reduced maintenance activity.
There were no commits and no active maintainers in the last three months, following a long gap since the latest release. This raises abandonment and responsiveness risk.
Composer build tooling is present, but no security scanning tools were detected. For a package that ships a Windows executable, the lack of scanning reduces transparency and assurance.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear, a meaningful transparency gap for a package that installs and runs a native Windows service.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/queue Version 5.5.*|5.6.*|5.7.*|5.8.*|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/console Version 5.5.*|5.6.*|5.7.*|5.8.*|^6.0|^7.0|^8.0|^9.0|^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.