Clear packaging and a matching repository make the release easy to inspect. The project is small and early-stage, so long-term maintenance capacity remains unproven.
68%
Total Score
50
100
88
100
One registry maintainer is workable for a small package, but it leaves limited publishing redundancy when combined with the repository's concentrated activity.
The package and repository are owned by the same user account, which supports ownership continuity, but it does not provide organization-level maintenance redundancy.
This is a very new package, released once 80 days ago, so there is not enough history to establish a durable release pattern. Its young age partly explains the limited evidence rather than indicating abandonment by itself.
One contributor made all three commits in the last three months, creating a clear single-person maintenance dependency. The repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.
The repository recorded three commits in the last three months, showing some recent activity but a very light maintenance cadence for a package whose only release is recent.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^12.0 || ^13.0 | — | — |
illuminate/support Version ^12.0 || ^13.0 | — | — |
illuminate/database Version ^12.0 || ^13.0 | — | — |
illuminate/contracts Version ^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.