Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for any team deploying agent workloads that touch real systems: pin down a written policy once, point Ironcurtain at your agent binary, and walk the audit log to confirm the policy actually blocks the calls you intended before promoting it to production.
Who should use it
Who should skip it
Skip provos/ironcurtain if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
provos/ironcurtain is tracked by RepoRadar as a developer tool in the Radar 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 moderate setup difficulty. provos/ironcurtain leads on workflow potential (9.3) and open-source/build quality (8.4); its lowest signal is setup ease (6.4), so factor that in before investing setup time. 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 provos/ironcurtain record combines a 7.8/10 composite score with separate popularity (78.0), risk (none), and setup (moderate) 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
policy enforcement is only as good as the constitution you write; review it like a security policy, not a prompt; running agents under any sandbox is still a learning workflow; treat early runs as untrusted.