GitHub Integration

Mapnostics connects to GitHub via OAuth to read your repositories, file contents, and commit history. All access is strictly read-only — we never modify your code, create branches, or push commits.

Authentication

Sign in with GitHub at mapnostics.com/login. You will be redirected to GitHub's OAuth flow, which asks for the permissions Mapnostics needs. After granting access, you are redirected back to your dashboard.

Permissions requested

• read:user — your GitHub username and email, used for account identification.
• repo (scope) — read access to your repositories, including private ones. We only read; we never write.
• read:org — read access to organization repos if you connect an org-owned repository.

Repository types

Public repositories

Available on all plans including Free. Anyone can connect a public GitHub repository without any special configuration.

Private repositories

Available on Pro and Team plans. Requires OAuth authentication with repo scope. Indexed code is stored encrypted at rest in our database and used only to power your analyses — it is never shared, used for training, or exposed to other accounts. Deleting a repository (or your account) permanently purges every stored chunk of its code.

Organization repositories

For repos under a GitHub organization, the org admin may need to approve the Mapnostics OAuth app. This is a one-time step. Contact your GitHub org admin or reach out to us for setup guidance.

Git history

Mapnostics reads commit metadata for each file — when it last changed and how long it has gone untouched. This data is used to identify file activity patterns and surface zombie code (code that exists but has had no recent changes despite the surrounding code evolving). The unused-file threshold defaults to 90 days and is configurable per repository.