known-bad vs analyzing-experiment-session-replays

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

Metricknown-badSkill analyzing-experiment-session-replaysSkill

Type: known-badSkill; analyzing-experiment-session-replaysSkill
Category: known-badOther; analyzing-experiment-session-replaysOther
GitHub stars: known-bad0; analyzing-experiment-session-replays65
Trust scoreⓘAuditability and maintenance signals — not a security audit.: known-badNot yet assessed; analyzing-experiment-session-replays73/100 · Good
Community rating: known-badNo reviews yet; analyzing-experiment-session-replaysNo reviews yet
Last commit: known-badUnknown; analyzing-experiment-session-replays3 days ago
Licence: known-badNone declared; analyzing-experiment-session-replaysNone declared
Official: known-badNo; analyzing-experiment-session-replaysNo
Source: known-bad Repository; analyzing-experiment-session-replays 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.