Tests, documentation, and a matching source repository provide a solid starting point. However, one release in about six months with no commits in the last three months leaves maintenance capacity unproven, and no security policy adds a smaller transparency gap.
62%
Total Score
50
88
50
The package has only one release, published about six months ago, so there is too little history to establish sustained maintenance. This is partly offset by the repository still being present and unarchived.
There were no commits and no active maintainers in the last three months, despite the repository being about six months old. That makes ongoing maintenance capacity unproven.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's README and tests provide some transparency but do not replace that policy.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^12.0 | — | — |
illuminate/queue Version ^12.0 | — | — |
illuminate/support Version ^12.0 | — | — |
illuminate/database Version ^12.0 | — | — |
illuminate/contracts Version ^12.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.