Documentation, tests, and licensing are solid. The single-person project has no security policy, limiting visible support and incident-response capacity.
61%
Total Score
50
100
88
75
Only one registry publishing maintainer is listed, leaving limited visible publishing redundancy for an individually owned project.
There were no commits and no active maintainers during the last three months, indicating a meaningful recent maintenance gap despite the earlier release cadence.
Composer build tooling is present, but no security-scanning tools are reported, leaving a repository hygiene gap.
No security policy is present, so the project does not document a clear vulnerability reporting or response process.
The assessed release is not marked prerelease, but it remains below major version 1, so API maturity is not fully established.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
web-token/jwt-framework Version ^3.2 | — | — |
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.