Documentation, tests, and a matching MIT license make integration easier. Organization backing and a release note help, but workflow references are not pinned and no security policy is published.
62%
Total Score
75
50
83
75
Twelve runtime dependencies, including network, process, and serialization-related components, create a moderately broad dependency surface for this library. The profile is not severe by itself, but it increases the amount of upstream behavior to maintain.
The package has only one release, published about five months ago, so there is not enough release history to establish sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only about five months old, this leaves maintenance continuity unproven.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this modestly reduces external validation but is not decisive for a new package.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning layer is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0|^2.0|^3.0 | — | — |
opis/closure Version ^3.0|^4.0 | — | — |
psr/container Version ^1.0|^2.0 | — | — |
psr/simple-cache Version ^1.0|^2.0|^3.0 | — | — |
guzzlehttp/guzzle Version ^6.0|^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.