Codescene vs Auto Mobile
These two are level on the tashan score (within 2 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 ›
| Codescene | Auto Mobile | what it means | |
|---|---|---|---|
| tashan score | 75 | 73 | upkeep + freshness, gated by adoption |
| Adoption evidence | 2k/wk | 5k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 99 | 73 | cadence, maintainers, status |
| Expertise grade | not graded | thin | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | NOASSERTION | — | |
| Maintainers | more than one | one primary | bus-factor risk |
Install either
Codescene
claude mcp add codescene-mcp-server -- npx -y @codescene/codehealth-mcpAuto Mobile
claude mcp add auto-mobile -- npx -y @kaeawc/auto-mobileNeither 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: Codescene · Auto Mobile.