Commit — Supply Chain Risk Scoring vs travel

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 travelMCP Server

Type: Commit — Supply Chain Risk ScoringMCP Server; travelMCP Server
Category: Commit — Supply Chain Risk ScoringLocation; travelLocation
GitHub stars: Commit — Supply Chain Risk Scoring0; travel0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Commit — Supply Chain Risk ScoringNot yet assessed; travelNot yet assessed
Community rating: Commit — Supply Chain Risk ScoringNo reviews yet; travelNo reviews yet
Last commit: Commit — Supply Chain Risk ScoringUnknown; travelUnknown
Licence: Commit — Supply Chain Risk ScoringNone declared; travelNone declared
Official: Commit — Supply Chain Risk ScoringNo; travelNo
Source: Commit — Supply Chain Risk Scoring Repository; travel 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.