investigate-incident vs mp-connect

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

Metricinvestigate-incidentCommand mp-connectCommand

Type: investigate-incidentCommand; mp-connectCommand
Category: investigate-incidentSecurity; mp-connectSecurity
GitHub stars: investigate-incident0; mp-connect0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: investigate-incidentNot yet assessed; mp-connectNot yet assessed
Community rating: investigate-incidentNo reviews yet; mp-connectNo reviews yet
Last commit: investigate-incidentUnknown; mp-connectUnknown
Licence: investigate-incidentNone declared; mp-connectNone declared
Official: investigate-incidentNo; mp-connectNo
Source: investigate-incident Repository; mp-connect 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.