Frihet ERP vs Opentax
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 ›
| Frihet ERP | Opentax | what it means | |
|---|---|---|---|
| tashan score | 69 | 67 | upkeep + freshness, gated by adoption |
| Adoption evidence | 1k/wk | 1k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 72 | 64 | cadence, maintainers, status |
| Expertise grade | deep | deep | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script, 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 | one primary | bus-factor risk |
Install either
Frihet ERP
claude mcp add frihet-mcp-server -- npx -y @frihet/mcp-serverOpentax
claude mcp add invaro-opentax -- npx -y @invaro/opentaxNeither 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: Frihet ERP · Opentax.