Healthy overall, with caveats. It has recent releases, tests, a clear README, an active unarchived repository, and a clean release process, but maintenance is concentrated in one contributor and the project has little visible adoption and no security policy.
78%
Total Score
75
100
89
67
All five commits in the last three months came from one contributor, leaving a concentrated maintenance path. Organization backing provides some handoff capacity, but no second active contributor is shown.
The repository has only 1 star, 0 forks, and 1 watcher, which is weak supporting evidence for maturity and community resilience, although popularity alone does not make a small maintained package unsafe.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest transparency and vulnerability-monitoring gap.
The repository has no SECURITY.md or other detected security policy, making vulnerability reporting and disclosure expectations less transparent.
Neither workflow declares top-level token permissions. No workflow requests top-level write access, and the clean workflow-risk profile limits the practical concern, but explicit least-privilege settings would be stronger.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
lenius/basket Version ^5.0 | — | — |
illuminate/auth Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
illuminate/container Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.