GitHub
Connect repositories to extract project metadata, languages, and verifiable portfolio evidence.
Overview
GitHub is the home for developers and modern open-source software engineering. Applivo's GitHub integration extracts verifiable technical evidence—including public repositories, programming language distributions, architecture notes, and primary framework dependencies—to substantiate technical claims in your applications and furnish authentic context for AI screening answers.
Built on least-privilege principles, the integration requests only read-only user access (read:user), ensuring Applivo can never write to your repositories, delete commits, or modify private code.
Configuration
Connecting GitHub requires user authorization via GitHub OAuth App:
- Navigate to Dashboard → Connections.
- Locate GitHub under Developer profiles.
- Click Connect to open GitHub's official authorization screen.
- Review the requested read-only permissions: 'Read access to user profile data'.
- Click Authorize applivo-app. GitHub redirects to GET /api/integrations/github/callback.
- Applivo exchanges the authorization code for an encrypted access token and imports your public repository index.
- The card displays your GitHub username, avatar, and repository count.
How it works
The GitHub service (app/services/integrations/github.py) analyzes your developer profile:
- 1. Repository Ingestion: Fetches metadata for your non-forked public repositories (name, description, primary language, star count, topics).
- 2. Language Percentiles: Aggregates bytes per language across repositories to calculate authentic language proficiency percentages (e.g., Python 48%, TypeScript 32%, Rust 20%).
- 3. README Extraction: Analyzes repository README documents to understand system architectures, APIs, and tools used.
- 4. Answer Enrichment: When a job asks 'Describe a challenging project you built in TypeScript', Lumi retrieves authentic project details from your GitHub repositories to formulate a truthful, evidence-backed response.
Available features
- Read-only sync of public repositories and project hierarchies.
- Automatic language distribution calculation and primary framework extraction.
- README and architectural context extraction for AI answer drafting.
- Automated repository link insertion in technical application fields.
Permissions and data access
Requests read:user scope. Private repositories, organization secrets, and code commits are completely excluded from access.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Repositories not displaying in profile | Repositories are private or candidate account has zero public non-forked repos | Mark target showcase repositories as public on GitHub. |
| OAuth returns 'Redirect URI mismatch' | GITHUB_CLIENT_ID or GITHUB_CLIENT_SECRET misconfigured on server | Verify redirect callback URL in GitHub OAuth App settings. |
Frequently asked questions
Can Applivo see my private repositories?
No. The read:user scope only permits access to public profile data and public repositories. Private code remains completely inaccessible.
Related articles
- OpenRouter AI EngineApplivo's internal multi-model reasoning gateway routing candidate profiling across state-of-the-art LLMs.
- ATS Resume IntelligenceNative keyword match scoring, format compliance auditing, and role-tailored resume generation.
- Integrations directory & ecosystemConnect your career stack with Applivo across job boards, browser automation, cloud vaults, scheduling, and notifications.