The package is MIT-licensed, documented, and has a small runtime dependency surface. Its single-person project has little release history and no recent commit activity or security policy, making ongoing support less certain.
61%
Total Score
50
100
86
83
One registry maintainer is consistent with a small user-owned project, but it leaves little visible redundancy if that maintainer becomes unavailable.
Only two releases have appeared in about 200 days, with roughly 200 days between them. That is limited evidence of an established maintenance rhythm for a young package.
There were zero commits and zero active maintainers in the last three months. Even with a recent repository push, this provides weak evidence of sustained ongoing development.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a release-blocking issue.
The repository has no security policy, so users are given no documented channel or process for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support 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.