The project includes tests, a changelog, a clear license, and a matching repository. Its single-person ownership, absent recent development, no security scanning, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
62%
Total Score
38
100
78
75
The repository recorded zero commits and zero active maintainers over the past three months. This is the strongest maintenance concern and raises the risk that development has stalled.
One registry account has publish access. The repository is user-owned rather than organization-backed, so the narrow publishing base provides little redundancy if the maintainer becomes unavailable.
The registry namespace and repository are owned by the same individual user account, confirming ownership alignment but not providing organizational backing or maintainer redundancy.
Fourteen releases were published within roughly one day, showing active initial iteration, but the short history provides limited evidence of long-term maintenance.
There were no new or closed issues or pull requests in the past month. With no other recent collaboration activity shown, this weakens evidence of ongoing community maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/notifications Version ^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.