GitHub Lines

Visualises line counts on GitHub's file list, so bloated files stand out.

A Chrome extension that puts a bar on GitHub's file list showing each entry's share of the lines in that directory. Let an AI write code for a while and one file tends to swell out of proportion to the rest - but GitHub's own listing shows you nothing but names, so you never see it happen. This makes it obvious in the browser, without cloning anything. WHAT YOU SEE - The bar - relative to the largest entry in that directory, so the top row is always full - The percentage - its actual share of the directory's total - Colour - continuous with the line count, from blue through green and amber to red. Amber at 500 lines and red at 800 by default; both configurable - Directories - deepening violet with the largest file inside them, so you can tell where something bloated is buried without opening it - Treemap - switches to a view where area is line count. Click a directory to drill into it - Lines | Size - read the same display in bytes. Switching costs no request CHOOSE WHEN IT COUNTS Manual (default) Fetches nothing when the page opens; counts when you press the button Automatic Counts as soon as the page opens Off Shows estimates from file size alone Manual is the default so that a page you merely passed through does not spend your API budget. In manual mode, the checkbox on each row narrows what gets fetched. WHAT IT DOES NOT COUNT - Files matching the default exclusion patterns, such as build output and lock files - Files marked linguist-generated or linguist-vendored in the repository's .gitattributes - Binary files The exclusion patterns are editable in the options. ACCESS TOKENS (OPTIONAL) It works on public repositories without one, but the GitHub API allows 60 requests an hour unauthenticated. A fine-grained token raises that to 5,000 an hour and reaches private repositories. The only permission it needs is Contents: Read-only. Press "Verify and fill in the owners" in the options and the accounts and organizations that token can actually read are filled in for you. If you keep separate accounts for personal and work, register several tokens and each repository owner is routed to the right one. PRIVACY - There is no server behind this extension. It talks to github.com and api.github.com, and nothing else - Your tokens and settings are stored only in your browser (chrome.storage.local) - Line counts are cached in your browser's IndexedDB. File contents themselves are never stored - No analytics, no advertising, no crash reporting - Every request to the GitHub API is a GET. It never writes Privacy policy: https://ebi-oishii.github.io/github-lines-site/privacy/ LIMITS - github.com only (GitHub Enterprise Server is not supported) - A "line" is what wc -l counts. Blank lines and comments are not told apart - On a repository large enough to exceed roughly 100,000 files, nested directory totals are incomplete, and it says so ALSO The interface follows your browser's language (English or Japanese), and can be pinned to one in the options. Free, with no ads and no in-app purchases. The source is published under Apache-2.0. https://github.com/ebi-oishii/github-lines