ClaudeSuperPower

code-assessment vs signals-scout-anomaly-detection

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

Type
code-assessmentSkill
signals-scout-anomaly-detectionSkill
Category
code-assessmentAnalytics
signals-scout-anomaly-detectionAnalytics
GitHub stars
code-assessment151
signals-scout-anomaly-detection65
Trust score
code-assessment87/100 · Excellent
signals-scout-anomaly-detection73/100 · Good
Community rating
code-assessmentNo reviews yet
signals-scout-anomaly-detectionNo reviews yet
Last commit
code-assessment2 days ago
signals-scout-anomaly-detection2 days ago
Licence
code-assessmentApache-2.0
signals-scout-anomaly-detectionNone declared
Official
code-assessmentNo
signals-scout-anomaly-detectionNo
Source
code-assessment Repository
signals-scout-anomaly-detection 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.