How dhanchintu07-eng/repolens works
RepoLens is a React application for turning a GitHub repository URL into an analysis dashboard. A user submits a URL; the app uses demo data for URLs containing “demo” or asks its GitHub service to fetch repository metadata, languages, the file tree, contributors, and commits. It then presents repository, technology, contributor, commit, architecture, and file-exploration views. The README describes only a Vite template, so product capabilities are inferred from the sampled UI and source; unsampled dashboard implementations are shown only where the app wires them in.
Main entry points: App.tsx App orchestrator · githubService.ts GitHub analysis service · LandingPage.tsx URL landing form · mockData.ts Demo analysis data
Components 13
User Entry
- URL landing form
src/components/landing/LandingPage.tsx - App orchestrator
src/App.tsx
Analysis Data
- GitHub analysis service
src/services/githubService.ts - Demo analysis data
src/services/mockData.ts - GitHub API
- Analysis data types
src/types/repo.ts
Dashboard Views
- Repository overview
src/components/dashboard/RepoDNA.tsx - Tech stack
src/components/dashboard/TechStack.tsx - Contributor DNA
src/components/dashboard/Contributors.tsx - Commit timeline
src/components/dashboard/CommitTimeline.tsx - Architecture map
src/components/dashboard/ArchitectureMap.tsx
Code Exploration
- File tree explorer
src/components/explorer/CodebaseExplorer.tsx
Other components
- Repository user
Connections 15
- Repository user → URL landing form: enters URL
- URL landing form → App orchestrator: submits URL
- App orchestrator → GitHub analysis service: requests analysis
- App orchestrator → Demo analysis data: uses demo data
- GitHub analysis service → GitHub API: fetches repository data
- GitHub analysis service → Analysis data types: returns analysis shape
- GitHub analysis service → App orchestrator: returns analysis
- Demo analysis data → App orchestrator: provides analysis
- App orchestrator → Repository overview: passes repository
- App orchestrator → Tech stack: passes repository
- App orchestrator → Contributor DNA: passes contributors
- App orchestrator → Commit timeline: passes commits
- App orchestrator → Architecture map: renders view
- App orchestrator → File tree explorer: passes file list
- File tree explorer → Analysis data types: uses file shape