Codebase Amplified Stats

Real lines-of-code statistics per language for GitHub repositories, with vendored and generated files filtered out.

WHAT IT DOES GitHub's language bar measures bytes and counts every file Linguist recognises. A minified vendor bundle, a generated protobuf or a lock file can dominate it while telling you nothing about the code someone actually wrote. Codebase Amplified Stats counts lines instead, separates code from comments, and throws the machine-written files out first. The result appears in GitHub's sidebar, right under the Languages section, on any repository you can read — public or private. HOW TO USE IT 1. Sign in with GitHub. Open the extension's options and click "Sign in with GitHub". Paste the code it copies for you, then authorise. Once, and no password is ever typed into the extension. 2. Open any repository, public or private. The panel appears in the sidebar right under Languages and starts counting on its own — there is no button to press. 3. Read the real numbers: lines of code per language, with vendored, generated and binary files already thrown out. "Refresh" re-counts the latest commit. WHAT MAKES THE NUMBERS TRUSTWORTHY • Excludes vendored paths, generated output, binaries and oversized files, using GitHub Linguist's own rules, and always reports how many files were excluded and why. • Counts with a character-level state machine that understands strings, nested block comments, raw strings, Python docstrings and CRLF — verified per file against cloc and tokei. • Fast: one repository costs four API requests and a single archive download. Results are cached per commit, and line counts are cached per file-content hash, so unchanged files are never counted twice. • No backend, no telemetry, no third parties. Everything runs in your browser. ABOUT THE PERMISSION GITHUB ASKS FOR Sign-in with GitHub is required, because every request the extension makes is authenticated — that is what lets it read your private repositories. GitHub will ask for the "repo" scope and describe it as full control of private repositories: that is GitHub's wording for the scope, not what this extension does. "repo" is the only classic OAuth scope that grants read access to private repositories at all, and GitHub offers no read-only equivalent. The extension only reads — it lists a repository's files and downloads an archive of them to count lines. Your token stays in this browser profile and is sent to GitHub and nowhere else.