Sextant — GitHub repository analytics

Sextant adds analytics and navigation to the GitHub pages you already visit. Nothing to open, nothing to configure for public repos — the panels appear in place. WHAT YOU GET - Lines of code: total SLOC, file count, and a per-language breakdown in the repository sidebar. - Repo health: stars, forks, last push, commit activity, open issues and pull requests, plus CI status for the current commit. - Dependency vulnerabilities: known CVEs affecting the packages in your manifests, looked up via osv.dev. - TODO counts: per-file TODO/FIXME badges in the file tree. - File tree sidebar: browse the whole repo without leaving the page, with CI-failure markers on affected files. - Pull request analyzer: PR size, changed-file categories, risk flags, and suggested reviewers based on who has touched those files recently. - Notification inbox: your GitHub notifications grouped and filterable, with mark-as-read in place. - Permission audit: who has admin access across an organisation's repositories. - Organisation dashboard: repository-level metrics across an org. - Command palette (Cmd+K / Ctrl+K): jump to recent repos, PRs, issues and files. - Optional AI assistant: ask Claude questions about a repository, or summarise a pull request. Off by default; requires your own Anthropic API key. HOW LINE COUNTING WORKS Three data sources, picked automatically: 1. The Sextant backend at sextant.octago.nl, when you have connected GitHub. Counts SLOC with the scc tool against a shallow, blob-filtered clone — accurate and fast on repositories up to 1181 MiB as GitHub reports them, and the only source that works on private repos. 2. codetabs.com (free public API), used only for a repository Sextant can confirm from the page is public. If it cannot confirm that, the request is skipped rather than sent. 3. A byte estimate from GitHub's languages API (labelled "≈") as a last resort. The credit line under each panel says which tier produced the number, so you always know whether you're looking at exact SLOC or a ballpark estimate. CONNECTING GITHUB Click "Connect GitHub" and approve the code Sextant shows you on GitHub's device page, or paste a fine-grained Personal Access Token with Contents: Read. The token is stored in your browser. It is sent to GitHub's API, and to the Sextant backend, which uses it in memory for a single request and discards it — it is never persisted server-side. WHAT LEAVES YOUR BROWSER If you enable the AI features and supply an Anthropic API key, the contents of the files you attach, including files in private repositories, plus PR diffs, PR and issue text and workflow-run details are sent to Anthropic. The request goes from your browser straight to api.anthropic.com with your own key; no Sextant server sees it. The AI features are off until you turn them on. Everything else works without them. More about Sextant: https://knaxly.dev/sextant/ Privacy policy: https://knaxly.dev/sextant/privacy.html