A clear README, working tests, an MIT declaration, and organization backing make the package easy to evaluate and maintain. The workflow uses two unpinned actions, and no security scanning is configured, so build hygiene remains weaker than its documentation.
60%
Total Score
75
100
88
75
The package is 75 days old with only one release, so there is too little release history to demonstrate sustained maintenance or compatibility discipline.
There were zero commits and zero active maintainers in the last three months, which is concerning for a package with only one release because ongoing maintenance is not yet demonstrated.
Composer build tooling is present, but no security scanning tools were detected; that leaves a repository hygiene gap without proving the package is unsafe.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities, though this is a moderate maturity gap rather than a severe risk.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned, which weakens reproducibility and build-supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hashids/hashids Version ^5.0 | — | — |
illuminate/support Version ^10.0|^11.0 | — | — |
illuminate/database Version ^10.0|^11.0 | — | — |
illuminate/contracts Version ^10.0|^11.0 | — | — |
illuminate/validation Version ^10.0|^11.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.