tres-recon-gaps vs fact-check-workflow

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

Metrictres-recon-gapsSkill fact-check-workflowSkill

Type: tres-recon-gapsSkill; fact-check-workflowSkill
Category: tres-recon-gapsAutomation; fact-check-workflowAutomation
GitHub stars: tres-recon-gaps0; fact-check-workflow0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: tres-recon-gapsNot yet assessed; fact-check-workflowNot yet assessed
Community rating: tres-recon-gapsNo reviews yet; fact-check-workflowNo reviews yet
Last commit: tres-recon-gapsUnknown; fact-check-workflowUnknown
Licence: tres-recon-gapsNone declared; fact-check-workflowNone declared
Official: tres-recon-gapsNo; fact-check-workflowNo
Source: tres-recon-gaps Repository; fact-check-workflow 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.