Zoho all in one for Laravel
68%
Total Score
50
100
94
75
One contributor made all recent commits, giving the project a 100% top-contributor share. Because the repository is user-owned rather than organization-owned, this concentration increases continuity risk.
Only 2 commits were recorded in the last 3 months, so recent maintenance activity is limited. The recent release history partly offsets this, but ongoing activity remains thin.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.
The repository has no security policy. For a package handling API credentials and tokens, this weakens the documented process for reporting and addressing security issues.
The only workflow was fully analyzed with no dangerous sinks or audit findings, but both action references are unpinned. That leaves build behavior exposed to future action changes despite otherwise clean workflow hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.