Verdict — Compliance for AI-Generated Code vs cobbles

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricVerdict — Compliance for AI-Generated CodeMCP Server cobblesMCP Server

Type: Verdict — Compliance for AI-Generated CodeMCP Server; cobblesMCP Server
Category: Verdict — Compliance for AI-Generated CodeSecurity; cobblesSecurity
GitHub stars: Verdict — Compliance for AI-Generated Code0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Verdict — Compliance for AI-Generated CodeNot yet assessed; cobblesNot yet assessed
Community rating: Verdict — Compliance for AI-Generated CodeNo reviews yet; cobblesNo reviews yet
Last commit: Verdict — Compliance for AI-Generated CodeUnknown; cobblesUnknown
Licence: Verdict — Compliance for AI-Generated CodeNone declared; cobblesNone declared
Official: Verdict — Compliance for AI-Generated CodeNo; cobblesNo
Source: Verdict — Compliance for AI-Generated Code Repository; cobbles Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.