It has tests, release notes, a clear license, and no install-time scripts. The small audience, single-contributor activity, missing security policy, and unpinned CI actions add maintenance and build-reproducibility caveats.
68%
Total Score
50
94
75
The latest registry release was in June 2023, with no releases in the last 12 months. That is a meaningful freshness concern for a dependency, although recent repository activity shows the project has not been entirely abandoned.
All 3-month commit activity came from one contributor, giving the project a high maintenance concentration risk. The linked repository is user-owned, so there is no organization backing shown to offset it.
The repository had only 1 commit in the last 3 months, so maintenance activity is minimal despite a recent push being observed. This weakens confidence in sustained support.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, but the package's small scope and other project tooling reduce its severity.
Both workflows were fully analyzed with no injection, credential, or other audit findings, but all 5 referenced actions are unpinned. The clean audit is positive while unpinned dependencies weaken build reproducibility.
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.