How adwaith-js/kabas works
KABAS is an instructor-facing Kanban assessment app: instructors sign in, manage GitHub/Jira team connections, then inspect normalized issues, workload metrics, and team-level analysis. The React client calls an Express API; the server stores team credentials/configuration, fetches board data from the platform APIs, normalizes issues, and calculates assessments. The README documents the API and JSON storage; sampled frontend and backend references support the main calls. Some dashboard details and optional caching behavior are unsampled, so those links are omitted where not established.
Main entry points: analysis.ts Analysis API · teams.ts Teams API · api.ts API client · routes.tsx App routes
Components 22
Instructor interface
- App routes
src/app/routes.tsx - Login
src/app/pages/Login.tsx - Team dashboard
src/app/pages/Dashboard.tsx - Team assessment view
src/app/pages/TeamDashboard.tsx - Assessment details
src/app/components - API client
src/app/services/api.ts
API and access
- Auth middleware
server/src/middleware/auth.ts - Login API
server/src/routes/auth.ts - Teams API
server/src/routes/teams.ts - Analysis API
server/src/routes/analysis.ts - Express server
server/src/index.ts
Assessment pipeline
- Analysis engine
server/src/analysis/AnalysisEngine.ts - Unified issues
server/src/models/UnifiedIssue.ts - Client outlier analysis
src/app/services/analysisEngine.ts
Platform integrations
- GitHub client
server/src/clients/GitHubAPIClient.ts - Jira client
server/src/clients/JiraAPIClient.ts
Team persistence
- Team store
server/src/storage/TeamStore.ts - teams.json
- Response cache
server/src/cache/ResponseCache.ts
Other components
- Instructor
- GitHub
- Jira
Connections 31
- Instructor → App routes: uses
src/app/routes.tsx - App routes → Login: routes to
src/app/routes.tsx - App routes → Team dashboard: routes to
src/app/routes.tsx - App routes → Team assessment view: routes to
src/app/routes.tsx - Login → API client: authenticates via
src/app/pages/Login.tsx - Team dashboard → API client: loads teams via
src/app/pages/Dashboard.tsx - Team assessment view → API client: loads analysis via
src/app/pages/TeamDashboard.tsx - Team assessment view → Assessment details: renders
src/app/pages/TeamDashboard.tsx - Team assessment view → Client outlier analysis: uses
src/app/pages/TeamDashboard.tsx - API client → Login API: HTTP login
README.md - API client → Teams API: HTTP teams
src/app/services/api.ts - API client → Analysis API: HTTP analysis
src/app/services/api.ts - Express server → Login API: mounts
server/src/index.ts - Express server → Teams API: mounts
server/src/index.ts - Express server → Analysis API: mounts
server/src/index.ts - Teams API → Auth middleware: protects routes
server/src/index.ts - Analysis API → Auth middleware: protects routes
server/src/index.ts - Teams API → Team store: reads and updates
server/src/routes/teams.ts - Analysis API → Team store: reads team config
server/src/routes/analysis.ts - Team store → teams.json: loads and saves
server/src/storage/TeamStore.ts - Analysis API → GitHub client: fetches issues
server/src/routes/analysis.ts - Analysis API → Jira client: fetches issues
server/src/routes/analysis.ts - Teams API → GitHub client: tests connection
server/src/routes/teams.ts - Teams API → Jira client: tests connection
server/src/routes/teams.ts - GitHub client → GitHub: queries
server/src/clients/GitHubAPIClient.ts - Jira client → Jira: queries
server/src/clients/JiraAPIClient.ts - GitHub client → Unified issues: normalizes with
server/src/clients/GitHubAPIClient.ts - Jira client → Unified issues: normalizes with
server/src/clients/JiraAPIClient.ts - Analysis API → Analysis engine: calculates with
server/src/routes/analysis.ts - Analysis engine → Unified issues: analyzes
server/src/analysis/AnalysisEngine.ts - Analysis API → Response cache: uses
server/src/routes/analysis.ts