A logger for the Laravel HTTP Client
72%
Total Score
caution
Usable with caveats: recent releases exist, but commit activity has stopped and workflow actions are unpinned.
The registry namespace and repository are owned by the same individual, providing direct ownership alignment. A single-person project has less organizational redundancy than an organization-backed project.
There were no commits and no active maintainers in the last 3 months. The recent v2.6.0 release partly offsets this, but the lack of current development activity remains a maintenance caution.
Only 2 issues and 2 pull requests are open, with no new or closed items in the last month. This is limited activity, but it does not by itself show abandonment given the recent release.
Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a hygiene gap rather than evidence of unsafe code.
The repository has no security policy. This reduces transparency for vulnerability reporting, though it is not by itself a dependency-blocking defect.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/support Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.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.