Google Cloud Logging For Laravel
78%
Total Score
83
94
75
All three recent commits came from one contributor, so maintenance continuity depends heavily on a single individual. Organization backing partly reduces handoff risk but does not remove the concentration concern.
Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and maintenance-process gap.
The repository has no security policy. That weakens vulnerability-reporting transparency, although the recent release activity and organization ownership provide some compensating context.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/cloud-logging Version ^1.34.0|^2.1.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.0 | — | — |
google/cloud-error-reporting Version ^0.26.0 | — | — |
spatie/laravel-package-tools Version ^1.14.1 | — | — |
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.