The package is brand new, with one release and no recorded commits in the last three months, so long-term maintenance is unproven. Repository tests, MIT licensing, build tooling, and security scanning provide useful foundations.
65%
Total Score
50
100
94
67
The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it provides less visible organizational backing for a brand-new package.
The package is 0 days old and has only 1 release, leaving no meaningful release track record or evidence of sustained maintenance.
There were 0 commits and 0 active maintainers in the last three months. Because the package is 0 days old, this mainly confirms that maintenance history is unproven rather than showing abandonment.
The repository has no security policy, which leaves vulnerability reporting and response expectations undocumented.
No GitHub Actions workflows were present, so there were no workflow findings; this also means no CI or release workflow evidence was available.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^13.0 | — | — |
illuminate/console Version ^13.0 | — | — |
illuminate/routing Version ^13.0 | — | — |
illuminate/support Version ^13.0 | — | — |
illuminate/database Version ^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.