BLOCKTRUST TrustScan vs uselessfacts
Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.
- Type
- BLOCKTRUST TrustScanMCP Server
- uselessfactsMCP Server
- Category
- BLOCKTRUST TrustScanOther
- uselessfactsOther
- GitHub stars
- BLOCKTRUST TrustScan0
- uselessfacts0
- Trust score
- BLOCKTRUST TrustScanNot yet assessed
- uselessfacts74/100 · Good
- Community rating
- BLOCKTRUST TrustScanNo reviews yet
- uselessfactsNo reviews yet
- Last commit
- BLOCKTRUST TrustScanUnknown
- uselessfacts58 days ago
- Licence
- BLOCKTRUST TrustScanNone declared
- uselessfactsMIT
- Official
- BLOCKTRUST TrustScanNo
- uselessfactsNo
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.