12306 vs Sem
12306 scores 3 points higher — a narrow lead. Read the evidence rows below before treating it as decisive. 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 ›
| 12306 | Sem | what it means | |
|---|---|---|---|
| tashan score | 72 | 69 | upkeep + freshness, gated by adoption |
| Adoption evidence | 7k/wk | 4k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 69 | 70 | cadence, maintainers, status |
| Expertise grade | not graded | deep | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories, runs an install script, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | — | MIT OR Apache-2.0 | |
| Maintainers | one primary | one primary | bus-factor risk |
Install either
12306
claude mcp add 12306 -- npx -y 12306-mcpSem
claude mcp add sem -- npx -y @ataraxy-labs/semNeither 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: 12306 · Sem.