multi-judge-consensus
Cross-vendor multi-model review committee that gates AI/agent-generated content before it ships — consensus-based hallucination defense. Zero dependencies, local-first CLI, MCP server, CI gate exit codes.
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- github:ElonAug7/multi-judge-consensus
- Listed in
- GitHub
- Publisher
- @elonaug7
- Published
- 2026-09-19
- License
- GPL-3.0
- Evidence
- Listed only, not analyzed yet
Source: https://github.com/elonaug7/multi-judge-consensus
What a full analysis of multi-judge-consensus checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.