The package is small and clearly documented, with repository tests and a matching source project. Its release cadence is active, but recent commit activity is absent and the lone maintainer and unpinned workflow references leave less maintenance and build assurance.
68%
Total Score
63
100
89
83
Only one registry account has publish access, which concentrates release responsibility and reduces resilience if that maintainer becomes unavailable.
The registry namespace and repository owner match, but the owner is an individual user rather than an organization, so there is no organizational backing to compensate for the single-maintainer base.
The repository recorded zero commits and zero active maintainers in the last three months. Although a release was published recently, the lack of recent source activity weakens confidence in ongoing maintenance.
The repository has 3 stars and no forks. This is limited adoption evidence, but popularity is supporting evidence and does not outweigh the package's other signals.
Composer is used for the build, but no security-scanning tool is detected. The missing scanner is a hygiene gap, not evidence that the package is unsafe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.67 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/database Version ^8.67 || ^9.0 || ^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.