Log10x vs Powerbi Modeling
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 ›
| Log10x | Powerbi Modeling | what it means | |
|---|---|---|---|
| tashan score | 74 | 73 | upkeep + freshness, gated by adoption |
| Adoption evidence | 6k/wk | 5k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 84 | 79 | cadence, maintainers, status |
| Expertise grade | thin | solid | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories | no known advisories, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | MIT | Microsoft | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Log10x
claude mcp add log10x -- npx -y log10x-mcpPowerbi Modeling
claude mcp add powerbi-modeling -- npx -y @microsoft/powerbi-modeling-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 — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Log10x · Powerbi Modeling.
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.
- The whole series behind any row, back to the first day we measured it
- The replacement, named — not just the news that something died
tashan doctorover your own config, on your own machine
Start a 7-day trial › Everything measured on this page stays free.