Commit — Supply Chain Risk Scoring vs SharpLens

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

MetricCommit — Supply Chain Risk ScoringMCP Server SharpLensMCP Server

Type: Commit — Supply Chain Risk ScoringMCP Server; SharpLensMCP Server
Category: Commit — Supply Chain Risk ScoringLocation; SharpLensLocation
GitHub stars: Commit — Supply Chain Risk Scoring0; SharpLens0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Commit — Supply Chain Risk ScoringNot yet assessed; SharpLensNot yet assessed
Community rating: Commit — Supply Chain Risk ScoringNo reviews yet; SharpLensNo reviews yet
Last commit: Commit — Supply Chain Risk ScoringUnknown; SharpLensUnknown
Licence: Commit — Supply Chain Risk ScoringNone declared; SharpLensNone declared
Official: Commit — Supply Chain Risk ScoringNo; SharpLensNo
Source: Commit — Supply Chain Risk Scoring Repository; SharpLens 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.