create-dashboard vs signals-scout-anomaly-detection

Type

create-dashboardSkill

signals-scout-anomaly-detectionSkill

Category

create-dashboardAnalytics

signals-scout-anomaly-detectionAnalytics

GitHub stars

create-dashboard30

signals-scout-anomaly-detection65

Trust scoreⓘAuditability and maintenance signals — not a security audit.

create-dashboard83/100 · Excellent

signals-scout-anomaly-detection73/100 · Good

Community rating

create-dashboardNo reviews yet

signals-scout-anomaly-detectionNo reviews yet

Last commit

create-dashboard3 days ago

signals-scout-anomaly-detection2 days ago

Licence

create-dashboardMIT

signals-scout-anomaly-detectionNone declared

Official

create-dashboardNo

signals-scout-anomaly-detectionNo

Source

create-dashboard 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.