The project is brand new, with only four releases and no recorded commits or active maintainers over the past three months. It has strong basics—tests, release notes, documentation, a matching repository, and an MIT license—but all three workflow actions are unpinned and the release is still pre-1.0.
68%
Total Score
50
79
67
The package is only 0 days old with four releases, all published within roughly one day, so there is not yet enough history to establish sustained maintenance.
No commits or active maintainers were recorded in the past three months. Because the project is newly published, this is partly explained by its age but still leaves maintenance capacity unproven.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a package intended for API integrations.
Version 0.2.2 is not a stable major release, indicating an API that may still change; it is not marked as a prerelease, which partly offsets the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2.0 || ^3.0 | — | — |
psr/http-message Version ^1.1 || ^2.0 | — | — |
guzzlehttp/guzzle Version ^7.8 || ^8.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.