How koushiksoma5/codeorbit works
CodeOrbit combines platform-stat collection with interview-readiness analysis. Users register and link LeetCode/Codeforces handles, then view a dashboard of platform metrics, leaderboard, history, topic mastery, charts, and readiness recommendations; settings update their profile. The Express API also supports scheduled hourly snapshots and LeetCode problem caching. The graph reflects documented capabilities and shown calls; some dashboard/API and integration details are documented in the README, while unsampled implementation details are not assumed.
Main entry points: index.js Express routes · updateStats.js Hourly collection · App.js App routing · Dashboard.js Stats dashboard
Components 16
React client
- App routing
client/src/App.js - Sign up
client/src/pages/Signup.js - Login
client/src/pages/Login.js - Stats dashboard
client/src/pages/Dashboard.js - Profile settings
client/src/pages/Settings.js
REST API
- Express routes
server/index.js - JWT auth
server/middleware/auth.js
Analysis and persistence
- Readiness scoring
server/utils/readinessEngine.js - Scoring rules
server/config/readinessConfig.js - Hourly collection
server/cron/updateStats.js - User records
server/models/User.js - Stat history
server/models/StatHistory.js - Problem cache
server/models/LeetCodeProblem.js
Platform integrations
- LeetCode APIs
- Codeforces API
Other components
- User
Connections 24
- User → App routing: uses
README.md - App routing → Sign up: routes to
client/src/App.js - App routing → Login: routes to
client/src/App.js - App routing → Stats dashboard: routes to
client/src/App.js - App routing → Profile settings: routes to
client/src/App.js - Sign up → Express routes: registers via
README.md - Login → Express routes: authenticates via
README.md - Stats dashboard → Express routes: requests stats
client/src/pages/Dashboard.js - Profile settings → Express routes: updates profile
client/src/pages/Settings.js - Express routes → JWT auth: guards routes
server/index.js - Express routes → User records: reads and writes
server/index.js - Express routes → Stat history: reads history
server/index.js - Express routes → Readiness scoring: computes readiness
server/index.js - Readiness scoring → Scoring rules: uses weights
server/utils/readinessEngine.js - Express routes → Problem cache: caches problems
server/index.js - Express routes → LeetCode APIs: fetches profile data
server/index.js - Express routes → Codeforces API: fetches submissions
server/index.js - Hourly collection → User records: loads accounts
server/cron/updateStats.js - Hourly collection → Stat history: writes snapshots
server/cron/updateStats.js - Hourly collection → Problem cache: pre-caches problems
server/cron/updateStats.js - Hourly collection → LeetCode APIs: fetches problems
server/cron/updateStats.js - Hourly collection → Codeforces API: fetches stats
server/cron/updateStats.js - Stats dashboard → Stat history: loads trend data
client/src/pages/Dashboard.js - Stats dashboard → Readiness scoring: requests report
README.md