skill-scanner vs test-remediation

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

Metricskill-scannerSkill test-remediationSkill

Type: skill-scannerSkill; test-remediationSkill
Category: skill-scannerSecurity; test-remediationSecurity
GitHub stars: skill-scanner2.4K; test-remediation0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: skill-scanner91/100 · Excellent; test-remediationNot yet assessed
Community rating: skill-scannerNo reviews yet; test-remediationNo reviews yet
Last commit: skill-scanner9 days ago; test-remediationUnknown
Licence: skill-scannerNOASSERTION; test-remediationNone declared
Official: skill-scannerNo; test-remediationNo
Source: skill-scanner 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.