cve-risk-score vs list-tests

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

Metriccve-risk-scoreSkill list-testsSkill

Type: cve-risk-scoreSkill; list-testsSkill
Category: cve-risk-scoreSecurity; list-testsSecurity
GitHub stars: cve-risk-score0; list-tests0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: cve-risk-scoreNot yet assessed; list-testsNot yet assessed
Community rating: cve-risk-scoreNo reviews yet; list-testsNo reviews yet
Last commit: cve-risk-scoreUnknown; list-testsUnknown
Licence: cve-risk-scoreNone declared; list-testsNone declared
Official: cve-risk-scoreNo; list-testsNo
Source: cve-risk-score Repository; list-tests 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.