Its MIT license, tests, README, and exact repository match make the package transparent and easy to inspect. The single maintainer and absent security scanning add modest concern.
42%
Total Score
25
100
79
75
The package has had only two releases, both in April 2016, with no releases in roughly 10 years. That strongly raises abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no activity since April 2016. This is a substantial maintenance concern.
Only one registry maintainer is listed, which limits apparent publishing redundancy. The linked repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concern.
Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe.
No security policy is present, leaving vulnerability-reporting expectations unclear. This is a secondary transparency gap alongside the much stronger inactivity concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/oauth2-client Version ^1.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.