earnings-quality-screen vs risk-assessment

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

Metricearnings-quality-screenCommand risk-assessmentCommand

Type: earnings-quality-screenCommand; risk-assessmentCommand
Category: earnings-quality-screenFinance; risk-assessmentFinance
GitHub stars: earnings-quality-screen0; risk-assessment0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: earnings-quality-screenNot yet assessed; risk-assessmentNot yet assessed
Community rating: earnings-quality-screenNo reviews yet; risk-assessmentNo reviews yet
Last commit: earnings-quality-screenUnknown; risk-assessmentUnknown
Licence: earnings-quality-screenNone declared; risk-assessmentNone declared
Official: earnings-quality-screenNo; risk-assessmentNo
Source: earnings-quality-screen Repository; risk-assessment 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.