Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers running Claude Code, Codex, or any MCP-speaking agent who wants a single chokepoint to see every model call, mask secrets on the way out, and route subagents to cheaper models while the planner stays on the strong one.
Who should use it
Who should skip it
Skip openguardrails/agentfw if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
openguardrails/agentfw is tracked by RepoRadar as a developer tool in the Agent Infrastructure section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for openguardrails/agentfw are workflow potential (9.9) and practical usefulness (9.0), while evidence quality (7.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The openguardrails/agentfw record combines a 8.4/10 composite score with separate popularity (78.0), risk (conditional), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
agentfw is a security chokepoint — run it carefully during upgrades and pin versions, since a misconfigured proxy can drop or rewrite legitimate traffic.