openalice-realtime
Architecture rating
Exemplary substrate adoption: @openalicelabs/realtime consumed by every OpenAlice front-end, manifest 100/drift 100, 0 circular deps, 0 dead imports, avg complexity 3.0 — uniform and clean.
Core competency: exponential backoff reconnection, subscription tracking and status events on the RealtimeManager — but 2 bare/broad catch blocks and no visible idempotency/dedup on resubscribe dampen the score.
Valid manifest (100) with clear summary, AGENTS.md and 9 @feature annotations, but README is a thin Atlas-card stub and 9 missing docstrings / 9 format flags leave the API under-documented in code.
Single vitest suite (manager.test.ts) with config present and CI-buildable dist, but only one test file for 9 features and no visible count/coverage of reconnect/backoff edge cases — graded conservatively for unknown breadth.
Emits connection status events (consumer-observable), but no metrics, tracing or structured logging in-library and no health probe (no https endpoint in manifest) — observability is delegated, not provided.
Client-side WS library: no authn/authz, SSRF, rate-limit or header surface of its own — connection auth delegated to consumers; backoff caps reconnection storms but no token-refresh/auth hooks visible, graded conservatively as mostly out-of-scope.
manifest_owns_tables=[] and zero migrations/schema — no DB, RLS, FK or GDPR surface; appropriately absent for a stateless front-end library but no evidence to score positively.
source · auto-grader-2026-06-16
Telemetry ribbon · last 90 days
1 eventNo @feature annotations recorded in this repo yet.