Arc 1 vs AI Agent Firewall
These two are level on the tashan score (within 0 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 ›
| Arc 1 | AI Agent Firewall | what it means | |
|---|---|---|---|
| tashan score | 71 | 71 | upkeep + freshness, gated by adoption |
| Adoption evidence | 3k/wk | 2k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 73 | 73 | cadence, maintainers, status |
| Expertise grade | not graded | solid | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories, runs an install script, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | — | Apache-2.0 | |
| Maintainers | one primary | one primary | bus-factor risk |
Install either
Arc 1
claude mcp add arc-1 -- npx -y arc-1AI Agent Firewall
claude mcp add ai-agent-firewall -- npx -y @fidacy/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: Arc 1 · AI Agent Firewall.