openalice-dashboard
Architecture rating
Manifest present and valid with clear summary; README describes purpose well; 17 @feature annotations; but roadmap score is 30/100 (weakest axis per Atlas) and 3 undeclared env vars indicate incomplete operational documentation.
Manifest declares zero owned tables (pure client, no own DB) which is correct architecture; however no inspector run means FK/constraint/RLS discipline cannot be verified for any proxy queries; score reflects clean separation but unverified client-side data handling.
Valid manifest, 17 features declared, manifest_valid=true shows substrate adoption; however env drift (3 undeclared vars) and drift score of 70/100 indicate convention gaps; no inspector AST data to assess code pattern uniformity.
Health probe returns 200 at 30ms latency which shows basic liveness exists; but no inspector evidence of structured logging, distributed tracing, or client-side error reporting; dashboard.blal.pro is probed by Atlas but app-level metrics are unconfirmed.
Pure client Next.js app with no own DB reduces attack surface, but 3 undeclared env vars (including NEXT_PUBLIC_AUTH_URL) signal auth config drift; no inspector data to confirm CSP headers, rate-limiting, or token handling; CI currently failing which may mask security regressions.
CI conclusion is 'failure' as of 2026-07-05 — broken build is a direct reliability signal; 97.5% 24h uptime (≈36 min downtime/day) is below production-grade; no inspector data on graceful shutdown, retries, or error boundaries in the Next.js app.
No inspector run means zero confirmed test count; CI is failing which suggests tests either don't pass or don't exist in sufficient coverage; E2E_BASE_URL as undeclared env var hints at e2e setup but broken CI negates any confidence.
source · auto-grader-2026-07-06
Telemetry ribbon · last 90 days
1 eventNo @feature annotations recorded in this repo yet.