The repository has no security policy, and both workflow actions are unpinned. The package is clearly documented and tested in the repository, but its very recent publication leaves little evidence of sustained maintenance yet.
62%
Total Score
50
100
88
75
Only one registry account has publish access, and the project backing is an individual user rather than an organization. This leaves limited visible publishing redundancy for a new package.
The registry namespace and repository are owned by the same individual account, so the package's source ownership is consistent. Individual ownership provides less organizational redundancy than an established project team.
The package is only 0 days old with three releases, and the median interval is about 15 minutes. That shows active initial publication but provides no evidence of sustained maintenance or release stability.
There are no commits or active maintainers recorded in the last three months. Because the repository and package are newly observed, this is weak abandonment evidence, but it still leaves sustained maintenance unproven.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest transparency and hygiene gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^12.0|^13.0 | — | — |
illuminate/cache Version ^12.0|^13.0 | — | — |
illuminate/console Version ^12.0|^13.0 | — | — |
illuminate/routing Version ^12.0|^13.0 | — | — |
illuminate/support Version ^12.0|^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.