A single maintainer, no security scanning, and no security policy reduce confidence in ongoing care. The recent release and matching repository show the project is still published and traceable.
62%
Total Score
67
100
94
75
One registry maintainer means the project has a thin publishing base and limited resilience if that person becomes unavailable. The repository is owned by the same individual, so this is consistent rather than misleading administrative metadata.
The repository recorded zero commits and zero active maintainers over the last three months, which is a meaningful maintenance warning. A release was published recently, but that does not show continuing development capacity.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version 5.5.*|5.6.*|5.7.*|5.8.*|6.*|^7.0|^8.0|^9.0|^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.