The project has only one recent contributor and no tests or security policy. MIT licensing, a matching repository, and an organization owner provide useful safeguards, but the long gaps between releases limit confidence.
62%
Total Score
67
71
75
The artifact has no README, tests, or changelog, and the repository also reports no tests or changelog. Missing tests and project documentation reduce transparency for a library, although the absence of tests or a changelog in the published artifact is normal packaging practice.
The package has only 3 releases since February 2023, with a median interval of about 20 months and one release in the last 12 months. The July 2026 release shows it is not abandoned, but the slow cadence limits maintenance confidence.
All 2 recent commits came from one contributor, creating a concentrated maintenance dependency. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository had 2 commits in the last 3 months, showing current activity, but this is a limited maintenance pace for a dependency.
The project uses Composer for builds, but no security scanning tools are reported, leaving automated security coverage unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
league/oauth2-client Version ^2.9 | — | — |
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.