The LGPL license, tiny dependency footprint, and organization-owned repository support straightforward use. Its maintenance appears effectively dormant, and the repository does not identify the package in its README, weakening confidence that this is the intended source.
38%
Total Score
50
100
63
50
The package has had only two releases, with the latest on August 3, 2015 and none in the last 12 months. For an OAuth client library, this long release gap is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release inactivity. This materially lowers confidence in ongoing maintenance.
The repository name matches the package, but its README does not mention the package. The name match avoids a strong mismatch concern, while the missing README reference leaves some uncertainty about source alignment.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a secondary transparency gap alongside the stronger maintenance concerns.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.