A clear README, tests, MIT licensing, and release notes make the package straightforward to evaluate and integrate. It lacks a security policy, and both workflow actions are unpinned, so maintenance and build integrity deserve extra attention.
62%
Total Score
50
100
83
50
Only one account has registry publish access. That is a meaningful support and continuity limitation for a user-owned project, although the repository and registry owner do match.
The package has five releases over about three years, with one release in the last 12 months and a median interval of about six months. That shows ongoing publishing but a relatively slow cadence.
There were no commits and no active maintainers in the last three months. Combined with the slow release cadence, this suggests limited current maintenance activity, though a recent release provides some compensation.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little external adoption or review signal.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and assurance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/translation 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.