Documentation and licensing are solid, with no install-time scripts and a repository that matches the package. Its maintenance record is still thin, and the project has no security policy or scanning setup.
62%
Total Score
50
100
88
75
The repository is owned by an individual rather than an organization; this is not inherently unhealthy, but it provides less visible backing for a package with no demonstrated follow-up activity.
The package has only one release, published about 4.5 months ago, so there is little release history to demonstrate sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, leaving no observed evidence of ongoing maintenance after the initial release.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users have no documented reporting path for vulnerabilities in a package that manages panel credentials and account operations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/console Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^10.0|^11.0|^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.