ride/app-varnish
The MIT license, focused dependency set, and clear README make its intended integration easy to understand. Organization backing and a non-archived repository provide some continuity, but the package offers little evidence of current care.
42%
Total Score
50
100
75
75
Health Score Breakdown
The latest release was published in October 2016, and there have been no releases in nearly 10 years despite the package remaining available. This is strong evidence of abandonment risk.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the nearly 10-year gap since its last release. No newer activity is provided to offset that concern.
Composer is used as the build tool, but no security scanning tool is detected. For a small package this is a hygiene gap, though it is less significant than the long period without maintenance.
The repository has no security policy. This limits disclosure transparency, but it is a secondary concern compared with the absence of recent releases and commits.
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/lib-log Version ^1.0.0 | — | — |
ride/lib-config Version ^1.0.0 | — | — |
ride/lib-varnish Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 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.