The MIT license, focused dependency set, and README make adoption straightforward. Repository security practice is undocumented, with no security policy or scanning tool reported.
42%
Total Score
0
100
64
83
The package has only two releases, both published within minutes on June 7, 2025, and none in the following 12 months. That long release gap is a meaningful abandonment concern.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the absent recent releases, this points to weak current maintenance.
The repository has zero stars, forks, and watchers. This is limited supporting evidence and does not independently determine health, but it offers no external adoption signal to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tools were reported. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For an authentication package handling OAuth/OIDC flows, the absence makes vulnerability reporting and maintenance practices harder to assess.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/cache Version ^3.0 | — | — |
psr/http-client Version ^1.0 | — | — |
firebase/php-jwt Version ^6.11 | — | — |
psr/http-factory Version ^1.1 | — | — |
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.