openalice-service-template
Architecture rating
This is the shared substrate itself: zero circular deps, 0 dead imports, avg complexity 1.60/max 8, 0 god-modules — clean uniform Axum scaffold meant to seed new services at B+.
Valid manifest (manifest 100, 5 features) with clear summary, README explains the fork-to-B+ rationale; weakened by 21 missing docstrings, 1 TODO, and 2 declared-unused env vars (PORT, RUST_LOG).
9 integration tests in tests/integration.rs covering health, readyz, auth-401, name validation (empty/too-long/valid), shared-state round-trip and 404 — good critical-path coverage for a template, though no DB/error-path or concurrency tests.
Bearer-token authz enforced (post_items_without_token_returns_401) plus input validation (empty/too-long name guards); but no rate-limiting, no security-headers, and no SSRF/injection guards evident — adequate template baseline, not hardened.
Liveness+readiness probes wired (health_returns_200_with_body_ok, readyz_returns_200) and structured logging via RUST_LOG; no metrics endpoint or tracing spans surfaced, and latest_health probe fails (no https endpoint in manifest).
Axum handlers return typed status codes (401/404/200) and request validation rejects bad input, but no evidence of SIGTERM graceful shutdown, request timeouts, retries, or idempotency — gaps for a 'production-grade' template claim.
manifest_owns_tables empty, no migrations dir, items held in shared in-memory state (items_round_trip_via_shared_state) — no schema, FK/constraints, RLS or tenant isolation; intentionally minimal for a template but data layer is effectively absent.
source · auto-grader-2026-06-16
Telemetry ribbon · last 90 days
1 eventNo @feature annotations recorded in this repo yet.