Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineers who run Claude Code, Codex, OpenClaw, Hermes Agent, or any MCP-speaking agent on a personal or shared machine and need a local firewall that keeps secrets off the wire (API keys, wallet keys, tokens) without switching agents or adopting a framework; for security-conscious users who want credential masking at the wire level (real keys never reach the upstream LLM provider, neve
Who should use it
Who should skip it
Move on from openafw/openafw if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
openafw/openafw is tracked by RepoRadar as a local ai agent firewall in the MIT local AI agent firewall (credential masking, section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Silver tier and review needed setup difficulty. Across RepoRadar's eight signals, openafw/openafw is strongest on workflow potential (8.8) and practical usefulness (8.1) and weakest on momentum (5.1) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned openafw/openafw a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 54.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
Risk label needs manual review.