CASE STUDY / DEVELOPER TOOLS
DevLens.
An authenticated developer workspace that combines public GitHub repository analysis, persistent user sessions, deterministic evidence and scoring, and optional AI interpretation.
OVERVIEW
Authentication, evidence, and interpretation stay separate.
Users authenticate through GitHub OAuth with PKCE, then analyze public repository evidence from README files, project structure, manifests, tests, CI, and licenses. Deterministic findings remain authoritative, PostgreSQL/Neon persists sessions and compatible analyses, and Gemini adds optional explanations and next-project recommendations.
ARCHITECTURE
Secure sessions surround an independent analysis core.
The Next.js and React frontend communicates with a FastAPI backend that owns GitHub tokens, OAuth state, and repository-analysis APIs. HttpOnly cookie sessions, immutable GitHub user IDs, CORS controls, token isolation, and PostgreSQL/Neon persistence keep authentication separate from the versioned deterministic scoring pipeline.
RELIABILITY
Keep evidence authoritative and credentials isolated.
When Gemini is unavailable, deterministic analysis and scoring remain useful. GitHub tokens stay in the backend, while request IDs, structured logs, provider error categories, bounded concurrency, cache freshness, and explicit limitations make production behavior inspectable.