Clear documentation, tests, release notes, and a balanced two-person recent contributor base add confidence. The missing security policy and repository/package naming mismatch leave transparency questions.
78%
Total Score
100
100
75
83
There have been 34 releases over roughly three years, but only two in the last 12 months, indicating a slower recent release cadence without evidence of abandonment.
The repository name differs from the package name and its README does not mention the package, creating uncertainty about the exact package-to-repository linkage despite the matching organization.
The repository uses Make and Composer build tooling, but no security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was found, which reduces transparency for reporting and handling vulnerabilities in a security-sensitive client library.
Version 0.10.0 is not a stable major release, but it is not marked as a prerelease and recent releases contain no prerelease share.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-client Version ^1.0 | — | — |
web-token/jwt-framework Version ^3.3 | — | — |
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.