The initial release burst was followed by no commits in the last three months, and the project has only one registry maintainer. Strong documentation, tests, licensing, and a stable release reduce the risk, but security tooling and repository activity remain limited.
64%
Total Score
50
100
83
75
Only one account has registry publish access. Because the repository is user-owned rather than organization-backed, there is limited visible publishing redundancy.
The package has 12 releases in its first 286 days, but the median interval is about 1 hour 22 minutes, indicating a concentrated initial release burst rather than an established cadence.
The repository recorded zero commits and zero active maintainers during the last three months, which is a meaningful maintenance concern for a package released less than a year ago.
The repository has two stars, no forks, and no watchers. This is weak supporting evidence of adoption, but popularity alone does not determine package health.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
illuminate/database Version ^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.