The project has no commits or active maintainers in the last three months, and its release history is only two releases old. A clear README, release notes, MIT declaration, and matching repository improve transparency.
58%
Total Score
25
100
86
75
There were zero commits and zero active maintainers in the last three months, a meaningful warning that maintenance may have stalled after the initial releases.
The repository is owned by an individual rather than an organization, so the small maintainer base is not offset by visible organizational backing.
Only two releases exist, both published within about two days, so the project has limited evidence of sustained maintenance despite a recent start.
Composer build tooling is present, but no security-scanning tooling is configured, leaving a modest transparency and maintenance gap.
The repository has no security policy, reducing guidance for reporting and handling vulnerabilities in a package that exposes application routes and database integrations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http 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.