openalice-chat-bridge

Features

Status

×archived

Last activity

—

Branch

—

Architecture rating

★★★★☆C1mo ago

consistency★★★★☆★A-

Quality 98/A with manifest, drift, code_health and features all 100, zero cycles and zero dead imports — uniform adoption of the shared manifest/substrate conventions.

observability★★★★☆B

Dedicated GET /health and GET /metrics endpoints exposed per manifest; tracing depth and structured-log coverage unconfirmed.

docs★★★★☆B-

Valid manifest with 65 @feature annotations plus AGENTS.md and a docs/ dir, but README is a stub (Atlas card link only) and 120 missing docstrings.

data layer★★★★☆C

Owns chat_messages via a single migration (0001) with tenant_id scoping and a GDPR export endpoint, but no RLS/FORCE or FK/constraint evidence and only one table/migration shown.

security★★★☆★☆C-

Ingests untrusted external chat (Twitch/YouTube/Kick/TikTok) and exposes POST /v1/send plus GET /internal/me/{tenant_id}/export.json, but no evidence of authn/authz, SSRF/injection guards, or rate-limiting — graded conservatively on absent signals.

reliability★★★☆★☆C-

0 bare/broad excepts is good, but max complexity 53, 13 god modules, 9 deep-nesting sites and 17 complexity flags signal fragile control flow; no graceful-shutdown/retry/idempotency evidence.

testing★★☆★☆☆F

No test directory or test files present (only migrations/0001_chat_messages.sql); inspector surfaces no tests — critical ingest/dispatch/write-back paths are untested.

source · auto-grader-2026-06-16

Telemetry ribbon · last 90 days

1 event

commitmanifestlifecyclekind

No @feature annotations recorded in this repo yet.