knaxly.dev

Sextant

Repository analytics on the GitHub pages you already visit. Lines of code, repo health, pull-request risk, dependency vulnerabilities and a file tree, rendered in place, for Chrome and Edge.

← knaxly.dev

Sextant reads the repository, pull request, issue and organisation pages you are already looking at and adds the numbers GitHub does not show you. There is nothing to open and nothing to configure for public repositories.

Chrome and Edge. Edge installs the same Chrome Web Store build. Firefox is not supported, and there is no Firefox build.

What it does

• Lines of code Total SLOC, file count and a per-language breakdown in the repository sidebar: real counts, not a byte estimate, when you have connected GitHub.
• Repo health Stars, forks, last push, commit activity, open issues and pull requests, and the CI status of the current commit, on one card.
• Pull request analysis PR size, changed-file categories, risk flags, and suggested reviewers based on who has touched those files recently.
• Dependency vulnerabilities Known vulnerabilities affecting the packages in your manifests, looked up through the Open Source Vulnerabilities database (osv.dev).
• TODO counts Per-file TODO and FIXME badges, so you can see where the unfinished work actually is.
• File tree sidebar Browse the whole repository without leaving the page, with markers on the files a failing CI check pointed at.
• Org-wide repo view Every repository in an organisation in one sortable list, with the same health signals, plus a permission audit showing who holds admin access.
• Notification inbox Your GitHub notifications, grouped and filterable, with mark-as-read in place.
• Command palette Cmd+K or Ctrl+K to jump to a recent repository, pull request, issue or file.
• AI chat, with your own key Ask Claude about a repository, or summarise a pull request. Off by default. It runs on an Anthropic API key you supply and bill, and it sends the files you attach to Anthropic; see below.

How the line counting works

Three sources, picked automatically, and the credit line under the panel always says which one produced the number:

1. The Sextant backend, when you have connected GitHub. Counts with the scc tool over a shallow clone that is deleted as soon as the count is done. Exact, and the only source that works on private repositories.
2. codetabs.com, a free third-party API, used only for a repository Sextant has confirmed from the page is public. If it cannot confirm that, it does not ask.
3. A byte estimate from GitHub's own languages API, also only when you have connected GitHub. Shown with a ≈ so you know it is a ballpark. Never leaves GitHub.

Two of those three need a connected account, so without one the middle source is the only one available, and because Sextant asks it only about a repository it has confirmed from the page is public, a private repository with no account connected shows no line count at all. That is deliberate: the alternative is publishing the repository's name to a third party to find out.

Connecting GitHub

Public repositories work with no setup. For private repositories and exact counts, open the extension's Options page and either click Connect GitHub for OAuth, or paste a fine-grained Personal Access Token with Contents: Read, the least-privilege option. The token is stored in your browser. The backend uses it in memory for a single request and discards it; it is never stored server-side.

What leaves your browser

The short version: no analytics, no telemetry, no advertising, no sale of your data. Sextant does not run on any site other than github.com.

The part that deserves your attention: if you turn the AI features on and supply an Anthropic API key, the contents of the files you attach (including files in private repositories) plus pull-request diffs, issue text and workflow-run details are sent to Anthropic. The AI features are off until you switch them on, and every other feature works without them.

The privacy policy sets out exactly what is stored, what is transmitted, to whom, and for how long, feature by feature. The terms of service cover the rest.

More

• Beta access: how early builds will be distributed.
• Feedback and bug reports: how to reach us.
• Issue tracker: the public tracker the feedback page routes to. Filing needs a GitHub account; security findings go through private vulnerability reporting instead.