Usable with caveats: the package is licensed, documented, tested in its repository, and clearly backed by a matching source project. However, it has had no registry release for about 3 years 7 months and no recent repository activity, while its workflow permissions and security-policy coverage are weak.
55%
Total Score
50
100
88
63
One workflow uses pull_request_target, which can be risky because it runs with elevated repository context. No untrusted checkout or script-injection patterns were detected, limiting but not removing the workflow concern.
The registry namespace and repository are owned by the same individual, so the package has direct project backing. This is consistent with a small open-source package, though it also leaves limited organizational redundancy.
The latest release was published about 3 years 7 months ago, and there were no releases in the last 12 months. This is a substantial maintenance concern for a package tied to a fast-moving API ecosystem.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old last push, this indicates current maintenance capacity is uncertain.
The linked repository is not archived, but its last push was about 3 years ago. The non-archived status is reassuring, while the stale repository state reinforces the maintenance concern from release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
openai-php/client Version ^0.3.0 | — | — |
illuminate/contracts Version ^10.0 | — | — |
spatie/laravel-package-tools Version ^1.14.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.