scan-triage vs test-remediation

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

Metricscan-triageSkill test-remediationSkill

Type: scan-triageSkill; test-remediationSkill
Category: scan-triageSecurity; test-remediationSecurity
GitHub stars: scan-triage0; test-remediation0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: scan-triageNot yet assessed; test-remediationNot yet assessed
Community rating: scan-triageNo reviews yet; test-remediationNo reviews yet
Last commit: scan-triageUnknown; test-remediationUnknown
Licence: scan-triageNone declared; test-remediationNone declared
Official: scan-triageNo; test-remediationNo
Source: scan-triage Repository; test-remediation 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.