Chrome DevTools vs Trusty Squire
Chrome DevTools scores 16 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 ›
| Chrome DevTools | Trusty Squire | what it means | |
|---|---|---|---|
| tashan score | 92 | 76 | upkeep + freshness, gated by adoption |
| Adoption evidence | 3.3m/wk | 3k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 98 | 99 | cadence, maintainers, status |
| Expertise grade | deep | deep | 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 | Apache-2.0 | MIT | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Chrome DevTools
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcpTrusty Squire
claude mcp add trusty-squire -- npx -y @trusty-squire/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: Chrome DevTools · Trusty Squire.
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.