The README explains installation and use, and the repository matches the package. A single maintainer and no security scanning make recovery and review less resilient.
43%
Total Score
25
100
81
50
Only three releases exist, and the latest was published over three years ago with no releases in the last 12 months. This is strong evidence of abandonment risk for a maintained integration package.
The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap. The inactive repository is not archived, but it is not showing current maintenance.
One registry maintainer is a thin operational base for a user-facing addon, leaving limited redundancy if maintenance is needed. The linked repository is also owned by an individual rather than an organization.
Composer build tooling is present, but no security scanning tools were detected. That reduces evidence of ongoing dependency and code-quality oversight.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though not a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
openai-php/laravel Version ^0.4.3 | — | — |
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.