The project is brand new, with one release and no recorded commits beyond its initial publication. It has tests, documentation, a changelog, a matching README mention, and no install scripts, but one maintainer, no security policy, and unpinned workflow actions add ongoing risk.
64%
Total Score
50
100
79
67
A single registry maintainer is a thin publishing base for a package without organizational backing, increasing continuity risk if that person becomes inactive.
This is a same-day package with one release and no established release cadence, so maintenance maturity is unproven rather than clearly abandoned.
There were no commits or active maintainers in the three-month window, but the package is only zero days old, so this does not yet demonstrate abandonment.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, which leaves vulnerability reporting and response expectations undocumented for a client handling OAuth tokens.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2.0 || ^3.0 | — | — |
psr/http-client Version ^1.0 | — | — |
psr/http-factory Version ^1.0 | — | — |
psr/http-message Version ^1.1 || ^2.0 | — | — |
psr/simple-cache Version ^2.0 || ^3.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.