No release or repository commit has appeared for nearly five years, and the repository has no security scanning. The MIT license, matching repository, README, and release notes improve transparency, but do not offset the maintenance gap.
42%
Total Score
0
75
50
The latest release was nearly five years ago, with no releases in the last 12 months. This is strong evidence that the package may be abandoned.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating no current maintenance capacity.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces assurance, though it is not evidence that the release is unsafe.
The repository has no security policy, leaving users without documented reporting and response guidance. This is a maintenance and transparency gap for an SDK handling OAuth credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
league/oauth2-client Version ^2.6 | — | — |
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.