cross-sector vs earnings-quality-screen

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

Metriccross-sectorCommand earnings-quality-screenCommand

Type: cross-sectorCommand; earnings-quality-screenCommand
Category: cross-sectorFinance; earnings-quality-screenFinance
GitHub stars: cross-sector0; earnings-quality-screen0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: cross-sectorNot yet assessed; earnings-quality-screenNot yet assessed
Community rating: cross-sectorNo reviews yet; earnings-quality-screenNo reviews yet
Last commit: cross-sectorUnknown; earnings-quality-screenUnknown
Licence: cross-sectorNone declared; earnings-quality-screenNone declared
Official: cross-sectorNo; earnings-quality-screenNo
Source: cross-sector Repository; earnings-quality-screen 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.