The README, version release notes, stable versioning, and lack of install-time scripts improve transparency and reduce installation surprises. No security policy and no security scanning leave practices less visible for a package handling AI provider credentials.
58%
Total Score
75
100
88
75
All four releases arrived on 18 October 2025, with a median interval of about 32 minutes, showing an initial burst rather than an established release cadence.
The repository recorded zero commits and zero active maintainers in the last 3 months, which is a meaningful maintenance and abandonment concern for a young package.
Composer build tooling is present, but no security scanning tools were detected, leaving automated security checks absent.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
No GitHub Actions workflows were present to audit, so there are no workflow risks, but CI and automated release safeguards are also not evidenced.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.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.