CLI library of the Ride framework
62%
Total Score
75
81
75
The package has 13 releases since May 2016, but none in the last 12 months; its latest release was in June 2024, more than two years before collection. This materially raises abandonment risk despite a previously regular median release interval of about 46 days.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for absent recent activity.
The linked repository name does not match the package name and its README does not mention the package. A mismatch can be normal for a monorepo, but the absence of a README mention makes package ownership less transparent.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, although it is less severe for a small CLI library than for security-sensitive infrastructure.
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.