The package has a clear README, matching repository, repository tests, and a stable release. A single maintainer and no security policy reduce confidence for long-lived production use.
63%
Total Score
67
100
88
83
Registry publishing access is held by one maintainer. For this user-owned, small package that is plausible, but it leaves limited visible continuity if the maintainer stops responding.
The package has six releases over roughly six years, but none in the last 12 months and the latest release was about 2 years and 5 months ago. This indicates slow or paused maintenance for a small stable package.
The repository had zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating currently inactive development.
The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanner is a modest transparency gap rather than evidence of unsafe code.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's narrow scope limits the practical impact.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/validation Version ^7.0|^8.0|^9.0|^10.0|^11.0 | — | — |
illuminate/translation Version ^7.0|^8.0|^9.0|^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.