Backlog vs Mediawiki
These two are level on the tashan score (within 1 points), so the score does not decide it. The evidence rows below are where they differ. 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 ›
| Backlog | Mediawiki | what it means | |
|---|---|---|---|
| tashan score | 75 | 74 | upkeep + freshness, gated by adoption |
| Adoption evidence | 32k/wk | 1k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 69 | 98 | cadence, maintainers, status |
| Expertise grade | deep | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | — | MIT | |
| Maintainers | one primary | more than one | bus-factor risk |
Install either
Backlog
claude mcp add backlog-mcp-server -- npx -y backlog-mcp-serverMediawiki
claude mcp add mediawiki-mcp-server -- npx -y @professional-wiki/mediawiki-mcp-serverNeither 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 — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Backlog · Mediawiki.
Both numbers above are today’s. Whichever you pick, the question that matters next is when it changes — and this page cannot know that. Pro keeps the series behind each capability, and names what to move to.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.