Usable with caveats: it has a clear MIT license, documentation, tests, and a matching source repository, but release activity stopped about eight months ago after a short burst of five releases. A single maintainer, no security policy, and no repository adoption make long-term support uncertain.
58%
Total Score
50
100
78
90
Only one registry publishing account is listed, and the project is user-owned rather than organization-backed. This creates a thin publishing and support base if that maintainer becomes inactive.
The registry namespace and repository owner correspond to the same user account, providing clear ownership, but there is no organizational backing to compensate for the single-maintainer model.
The package published five releases, all within roughly two weeks, but the latest release was about eight months ago. This suggests an immature project with uncertain ongoing maintenance.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible adoption provides no external confidence buffer for this young package.
Composer build tooling is present, but no security scanning tools are configured. This is a hygiene gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3|^7.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.