MIT licensing and three runtime dependencies keep the scope clear. A single registry maintainer and no security policy leave little evidence of ongoing support.
42%
Total Score
100
67
50
The artifact has no README, which makes a library harder to evaluate and integrate. The absence of tests and a changelog is normal for published artifacts and is not treated as a gap here.
The package has had no release in over three years, with zero releases in the last 12 months. That long pause is strong evidence of abandonment risk, despite five releases at launch.
Composer build tooling is present, but no security scanning tools were detected. That is a modest maintenance and assurance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package intended to be used as a dependency.
The assessed version is still an alpha, and all recent releases are prereleases. Consumers should expect unfinished APIs and limited stability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version ^4.2 | — | — |
illuminate/support Version ^9.19 | — | — |
illuminate/database Version ^9.19 | — | — |
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.