WaAPI Laravel Package
72%
Total Score
50
100
100
60
Five workflows were analyzed; one uses pull_request_target, but there are no untrusted checkouts or script-injection findings. The workflow profile merits review but does not show a severe issue from the collected indicators.
A post-autoload-dump lifecycle script is present. This is a potentially relevant install-time behavior, but the signal provides no evidence that it is unusually risky or unrelated to normal Composer package setup.
Only one registry account, WaAPI, has publish access. Because the repository owner is identified as a user rather than an organization, this creates some continuity and publishing-account concentration risk.
The repository is owned by the user account WaAPIapp rather than an organization. This does not invalidate the package, but it provides less demonstrated handoff capacity for a single-maintainer project.
All 2 recent commits came from a single contributor, with a 100% top-contributor share and one contributor total. Without organization backing, this is a meaningful bus-factor risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
waapi/waapi-php-sdk Version ^2.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0|^13.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.