It has a clear MIT license, a small dependency footprint, tests, and a repository that matches the package. The single-maintainer project has had no release or commit activity for over three years, so future compatibility support is uncertain.
58%
Total Score
50
83
88
One registry maintainer publishes the package, which leaves a thin visible publishing base for a project needing future fixes. The matching repository and existing tests provide some compensating transparency.
The package has only three releases and none in the last 12 months; its latest release was over three years ago. This is a meaningful maintenance concern, though the stable 2.1.0 release may suit an unchanged integration.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. The repository is not archived, but current maintenance capacity is not demonstrated.
The repository has zero stars and forks and one watcher, providing little community evidence or backup for maintenance. Low popularity is supporting evidence rather than a standalone reason to reject a small, stable package.
Composer build tooling is present, but no security-scanning tooling is reported. The missing scanner is a hygiene gap, while the build configuration supports reproducible project maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/oauth2-client Version ^2.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.