A clear MIT license, focused dependencies, tests in the repository, and a release note support adoption. The missing security policy and unpinned workflow actions leave maintenance and build-integrity gaps to account for.
68%
Total Score
50
100
94
67
The repository is owned by an individual rather than an organization, so the single registry maintainer is not offset by visible organizational backing. The package nevertheless has a matching, dedicated repository and a recent release.
The repository recorded 0 commits and 0 active maintainers during the last 3 months. Although a release was published recently, the lack of recent source activity raises abandonment risk.
There are only 3 open issues and no pull requests, with no issue or pull-request activity in the last month. This is a modest maintenance concern, though the recent release provides some compensation.
Composer is used for builds, but no security scanning tools are configured. For a dependency library, that is a real but limited repository hygiene gap.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it does not by itself indicate that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^12.55|^13.1 | — | — |
illuminate/database Version ^12.55|^13.1 | — | — |
illuminate/contracts Version ^12.55|^13.1 | — | — |
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.