Cloudflare · @cloudflare vs Kubernetes
Kubernetes scores 39 points higher on the same evidence, which is a real separation rather than noise. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| Cloudflare · @cloudflare | Kubernetes | what it means | |
|---|---|---|---|
| tashan score | 46 | 85 | upkeep + freshness, gated by adoption |
| Adoption evidence | 40k/wk | 20k/wk | the raw public signal the score came from |
| Last release | abandoned | active | npm publish or repo push |
| Upkeep | 67 | 99 | cadence, maintainers, status |
| Expertise grade | not graded | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | Apache-2.0 | MIT | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Cloudflare · @cloudflare
claude mcp add cloudflare-mcp-server-cloudflare -- npx -y @cloudflare/mcp-server-cloudflareKubernetes
claude mcp add mcp-server-kubernetes -- npx -y mcp-server-kubernetesNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each, including what a licence adds, is on its own page: Cloudflare · @cloudflare · Kubernetes.