It has a clear MIT license, tests, documentation, and a small dependency surface. Maintenance evidence is weak, with no recent commits and no release since 2017; the absent security policy adds a smaller transparency concern.
52%
Total Score
50
100
81
75
The repository is owned by an individual account rather than an organization, and no broader project backing is shown. That leaves a relatively thin continuity model for a package with no recent release activity.
The latest release was about 9 years ago, and there have been no releases in the last 12 months. This is a substantial maintenance concern for a dependency, despite the package having four releases overall.
There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this indicates weak current maintenance capacity.
There were no new or closed issues or pull requests in the last month, with one issue still open. This is limited activity rather than proof of abandonment, but it provides little evidence of active support.
The repository has 3 stars and 3 forks, so community adoption and external review are limited. Popularity is supporting evidence only and does not by itself make the package unsafe to depend on.
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.