secret-safe-env vs cobbles

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

Metricsecret-safe-envMCP Server cobblesMCP Server

Type: secret-safe-envMCP Server; cobblesMCP Server
Category: secret-safe-envSecurity; cobblesSecurity
GitHub stars: secret-safe-env0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: secret-safe-envNot yet assessed; cobblesNot yet assessed
Community rating: secret-safe-envNo reviews yet; cobblesNo reviews yet
Last commit: secret-safe-envUnknown; cobblesUnknown
Licence: secret-safe-envNone declared; cobblesNone declared
Official: secret-safe-envNo; cobblesNo
Source: secret-safe-env 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.