Frequent releases, a current repository, and substantial recent commit activity support ongoing work. The project has no security policy or scanning, and its dependency profile remains small and understandable.
68%
Total Score
67
100
72
67
The manifest declares a proprietary license, with no detected license text or license file in the package or repository. That creates a material adoption and redistribution constraint for an open-source dependency.
Both the registry namespace and repository owner are the same individual account, with no organization ownership shown. This is consistent ownership but offers no organizational maintenance redundancy.
All 112 recent commits came from one contributor, leaving maintenance highly dependent on a single person. The repository owner is an individual account, so no organization backing is shown to compensate for that concentration.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers external validation but does not outweigh the observed maintenance activity.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning reduces assurance around ongoing maintenance hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http 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.