Auto Mobile vs Fiori
Fiori scores 14 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 ›
| Auto Mobile | Fiori | what it means | |
|---|---|---|---|
| tashan score | 73 | 87 | upkeep + freshness, gated by adoption |
| Adoption evidence | 5k/wk | 110k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 73 | 100 | cadence, maintainers, status |
| Expertise grade | thin | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | — | — | |
| Maintainers | one primary | more than one | bus-factor risk |
Install either
Auto Mobile
claude mcp add auto-mobile -- npx -y @kaeawc/auto-mobileFiori
claude mcp add fiori-mcp-server -- npx -y @sap-ux/fiori-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: Auto Mobile · Fiori.