Healthy and reasonable to adopt, with minor maintenance and security-process caveats. It has a recent stable release, a real repository with tests and CI, and organization backing, but no commits in the last three months and no documented security policy.
78%
Total Score
88
100
93
75
The repository recorded zero commits and zero active maintainers in the last three months. This is the main maintenance caveat, although it is partly offset by the release on March 2, 2026.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a process gap, not by itself evidence that the package is unsafe to depend on.
The repository has no security policy, leaving reporting and response expectations undocumented. This lowers transparency but is not severe enough to make the package unfit.
All four workflows omit top-level token permissions, but none declares top-level write access. The configuration is less explicit than ideal without showing an excessive write privilege.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^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.