The package is small and clearly licensed, with a focused dependency set and a repository that identifies it in its README. Limited security tooling adds concern for a security integration.
38%
Total Score
75
80
50
The latest release was about 9 years and 11 months ago, with no releases in the last 12 months. Six releases show some prior history, but the long publication gap is a maintenance concern.
The repository has recorded zero commits and zero active maintainers in the last 3 months, and its last push was in October 2016. This strongly suggests current maintenance has stopped.
Composer build tooling is present, but no security scanning tools were detected. This is a modest process gap rather than evidence that the package is unsafe.
The linked repository has no security policy. That is a meaningful transparency gap for an OAuth security integration, especially alongside the absence of recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ride/app Version ^1.0.0 | — | — |
ride/web-base Version ^1.0.0 | — | — |
ride/web-security Version ^1.0.0 | — | — |
ride/lib-security-oauth Version ^1.0.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.