Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering managers, security and compliance teams, AI coding agent platform teams, and engineering orgs that need an accountability + drift-detection + DLP-audit surface for AI-written code without changing the agent's workflow. The durable differentiator is the passive decision graph + drift detection + DLP audit + provenance attestation — the right shape for any AI coding agent depl
Who should use it
Who should skip it
Skip Brain0-ai/brain0 unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Brain0-ai/brain0 is tracked by RepoRadar as a black box for ai-written code (p in the AI Coding Agents section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, Brain0-ai/brain0 is strongest on workflow potential (9.5) and practical usefulness (9.0) and weakest on momentum (6.0) — 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 Brain0-ai/brain0 a composite score of 8.0 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 'low' 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
The passive design reads git and the agent transcripts — the operator needs to confirm the agent transcripts are persisted on disk in the expected location (Codex + Claude Code are auto-discovered; OpenCode; Cursor; and other agents may need a transcript-path config).