Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams deploying Claude Code, Codex, or Cursor who need deterministic guardrails before letting agents touch secrets, package managers, or production-adjacent repos.
Who should use it
Who should skip it
Pass on LuD1161/agentjail if its scope or audience does not match what your team is building right now.
About this signal
LuD1161/agentjail is tracked by RepoRadar as a policy guardrail in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. LuD1161/agentjail leads on workflow potential (9.7) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. 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 LuD1161/agentjail a composite score of 8.6 out of 10, placing it in the Gold 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 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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
Hooks into live Claude Code, Codex, or Cursor tool calls and can block or log file, shell, and MCP actions, so first rollout should stay on non-production repos while policy scope is tuned; Install path starts a local policy daemon and hook chain on developer machines, so teams should review the default rules and audit-log location before wider deployment.