code-pattern-risk-scanner vs gcs

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

Metriccode-pattern-risk-scannerMCP Server gcsMCP Server

Type: code-pattern-risk-scannerMCP Server; gcsMCP Server
Category: code-pattern-risk-scannerCloud; gcsCloud
GitHub stars: code-pattern-risk-scanner0; gcs0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: code-pattern-risk-scannerNot yet assessed; gcsNot yet assessed
Community rating: code-pattern-risk-scannerNo reviews yet; gcsNo reviews yet
Last commit: code-pattern-risk-scannerUnknown; gcsUnknown
Licence: code-pattern-risk-scannerNone declared; gcsNone declared
Official: code-pattern-risk-scannerNo; gcsNo
Source: code-pattern-risk-scanner Repository; gcs 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.