ride/cli-varnish
The README and changelog explain the commands, while the organization-owned repository and focused four-package dependency set add useful context. Security scanning and a security policy are absent, so ongoing maintenance and transparency remain limited.
45%
Total Score
67
100
78
75
Health Score Breakdown
The package has had no release in more than eight years and no releases in the last 12 months, which is strong evidence of abandonment risk despite its four-release history.
There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive since October 2017.
The repository has zero stars and forks, with 11 watchers. Low adoption is supporting caution because there is little visible community activity to offset the maintenance gap.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance-hygiene gap.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities in this operational CLI package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Joris Vandeweerd |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ride/app Version ^1.0.0 | — | — |
ride/cli Version ^1.0.0 | — | — |
ride/app-varnish Version ^1.0.0 | — | — |
ride/lib-varnish Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 11 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.