Kubernetes · containers vs Vercel · zueai
Kubernetes · containers scores 62 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 ›
| Kubernetes · containers | Vercel · zueai | what it means | |
|---|---|---|---|
| tashan score | 84 | 22 | upkeep + freshness, gated by adoption |
| Adoption evidence | 15k/wk | 1k/wk | the raw public signal the score came from |
| Last release | active | abandoned | npm publish or repo push |
| Upkeep | 99 | 34 | 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 known advisories, no build provenance | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | Apache-2.0 | MIT | |
| Maintainers | more than one | one primary | bus-factor risk |
Install either
Kubernetes · containers
claude mcp add kubernetes-mcp-server -- npx -y kubernetes-mcp-serverVercel · zueai
claude mcp add vercel-mcp -- npx -y vercel-mcpNeither 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: Kubernetes · containers · Vercel · zueai.