Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
It is useful when a team wants visible alternatives, objections, and a final synthesis instead of one opaque assistant answer. The project is young, but the workflow is concrete and the README focuses on checkpoints, user interruption, auditability, and recovery rather than a vague agent demo.
Who should use it
Who should skip it
Skip loveramarois-byte/council-lab if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
loveramarois-byte/council-lab is tracked by RepoRadar as a code repository in the Multi-agent deliberation workspaces section. It was first seen on 2026-07-29 and last updated on 2026-07-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, loveramarois-byte/council-lab is strongest on workflow potential (9.3) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar captured from https://github.com/loveramarois-byte/council-lab. 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 loveramarois-byte/council-lab a composite score of 7.8 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 35.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
users may import sensitive documents or prompts into third-party model providers; multi-agent debate can create persuasive but still unverified conclusions; new project with limited adoption signal despite current maintenance.