The MIT license, clear README, matching repository, and small dependency set make integration straightforward. The package has had no registry release for nearly three years, while recent repository activity does not yet show a maintained release cadence; testing and security tooling are also absent.
65%
Total Score
83
100
88
50
The package has nine releases over about six and a half years, but none in the last 12 months and the latest registry release was nearly three years ago. This is a meaningful maintenance and freshness concern.
The repository shows zero commits and zero active maintainers in the three months before collection. Although a later push is visible in the repository status, the measured recent activity does not demonstrate an active maintenance cadence.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy. That weakens vulnerability-reporting transparency, though it is less serious for this small package than abandonment or deprecation would be.
No GitHub Actions workflows were present, so there are no workflow findings or exposed workflow permissions to assess. This also means there is no observed automated CI or release hygiene to compensate for the missing security tooling.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3|^7.0 | — | — |
illuminate/support Version ~5.5.0|~5.6.0|~5.7.0|~5.8.0|^6.0|^7.0|^8.0|^9.0|^10.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.