Usable with caveats: the package is actively released, licensed, tested in its repository, and not deprecated or archived. However, there were no commits from active maintainers in the last three months, and several automation workflows grant write access without a documented security policy.
68%
Total Score
67
100
100
60
One of four workflows uses pull_request_target, although no untrusted checkouts or script-injection patterns were detected. The privileged workflow adds some automation risk but is not severe on this evidence.
The package declares a post-autoload-dump Composer lifecycle script. This is an install-time execution point and deserves review, but the signal provides no evidence that the hook is harmful.
The repository is owned by an individual rather than an organization, so continuity depends on a small personal project owner. This is partly offset by the recent release, pull-request merges, and existing repository tooling.
The repository recorded zero commits and zero active maintainers in the last three months, despite a recent release and pull-request activity. That gap weakens evidence of ongoing hands-on maintenance.
The repository has no security policy. For a library that handles HTTP request and response logging, the absence reduces vulnerability-reporting transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/contracts Version ^10.0 || ^11.0 || ^12.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.