Over-Reach Detector vs uselessfacts

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

MetricOver-Reach DetectorMCP Server uselessfactsMCP Server

Type: Over-Reach DetectorMCP Server; uselessfactsMCP Server
Category: Over-Reach DetectorOther; uselessfactsOther
GitHub stars: Over-Reach Detector0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Over-Reach DetectorNot yet assessed; uselessfacts74/100 · Good
Community rating: Over-Reach DetectorNo reviews yet; uselessfactsNo reviews yet
Last commit: Over-Reach DetectorUnknown; uselessfacts58 days ago
Licence: Over-Reach DetectorNone declared; uselessfactsMIT
Official: Over-Reach DetectorNo; uselessfactsNo
Source: Over-Reach Detector Repository; uselessfacts 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.