Code Auditor 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 ›
| Code Auditor | Powerbi Modeling | what it means | |
|---|---|---|---|
| tashan score | 71 | 70 | upkeep + freshness, gated by adoption |
| Adoption evidence | 3k/wk | 4k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 73 | 75 | cadence, maintainers, status |
| Expertise grade | thin | solid | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories, no build provenance | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | — | — | |
| Maintainers | one primary | more than one | bus-factor risk |
Install either
Code Auditor
claude mcp add code-auditor -- npx -y code-auditor-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, including what a licence adds, is on its own page: Code Auditor · Powerbi Modeling.