MIT licensing, tests, a matching repository, and a small dependency set make integration straightforward. The unpinned CI actions and absent security policy add modest transparency and build-integrity concerns.
59%
Total Score
75
100
83
83
The latest release was about five years ago, with no releases in the last 12 months. This is a meaningful maintenance concern for a dependency, despite the package having four releases over its lifetime.
There were no commits or active maintainers in the last three months, indicating that current development activity has effectively stopped. This materially increases abandonment risk.
The repository has two stars and nine forks, showing limited visibility. This is supporting evidence of a small project, but it does not outweigh the direct maintenance signals.
The linked repository is not archived, but it was last pushed about five years ago. The non-archived status is positive, while the old push date is consistent with the maintenance concern shown by release activity.
The repository has no security policy. For a small OAuth provider, this is a modest transparency gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/oauth2-client Version 2.4.* | — | — |
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.