The package includes a clear MIT license, a substantial README, repository tests, and a changelog. Its single-day release history and no commits in the last three months reduce confidence in ongoing maintenance, while workflow dependencies are unpinned.
58%
Total Score
50
100
83
67
Only one registry publishing account is listed. The repository is also owned by an individual rather than an organization, so there is no provided backing signal to offset the thin maintainer base.
The registry namespace and repository owner are the same individual account, with no organization backing shown. This is consistent with the thin maintainer and activity signals.
There have been three releases, all within roughly 90 minutes on the first release day, with no subsequent release during the package's 181-day lifetime. That pattern gives little evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only 181 days old, that is meaningful evidence that maintenance may have stopped.
The repository has zero stars, forks, and watchers. This is weak supporting evidence rather than a verdict, but it offers no external adoption signal to compensate for the limited maintenance activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support 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.