OctoCounts - SLOC panel Github forget

SLOC stands for Source Lines of Code, a software metric used to measure the size of a program by counting the lines in its source code. Unlike raw line count, SLOC distinguishes between code lines, comment lines, and blank lines. OctoCounts reports SLOC at two levels: per programming language and as aggregate totals across the entire repository, using the open-source counter tokei.

OctoCounts downloads a compressed archive tarball rather than a full git clone with history, so the transfer covers the current source tree instead of the repository's entire history. Nothing needs to be installed — no git, no Rust toolchain, no tokei binary. Results are cached by commit SHA and tokei version, so repeated analysis of the same commit returns instantly.

Yes. OctoCounts has browser extensions for Chrome, Edge, and Firefox, all named OctoCounts – GitHub SLOC & Code Statistics. They add a compact SLOC card to GitHub repository sidebars showing total line count and analysis status; clicking the card opens the full panel with files, total lines, code lines, comment lines, and blank lines per language. The extension includes a local cache, and no GitHub account or API token is required.

Yes. OctoCounts is completely free to use for public GitHub repositories, with no account, API key, sign-up, or publicly documented rate limit. Both the web app and browser extensions are free with no premium tier. The backend is open source in Rust using Axum, the frontend is React with TypeScript, and the entire stack can be self-hosted.

OctoCounts uses tokei for language detection, which supports over 200 programming languages and file types, including Rust, Python, JavaScript, TypeScript, Go, Java, C, C++, C#, Ruby, Swift, Kotlin, PHP, and many more. tokei detects languages primarily by file extension, with fallback to shebang lines and content-based detection. OctoCounts automatically skips heavy generated folders before passing the archive to tokei.

Yes. OctoCounts supports three export formats: plain text copies a formatted table to the clipboard, JSON downloads the full structured report, and PNG downloads a 1200 × 630 image card showing the language breakdown. All three formats are generated client-side from the analysis data already loaded in the browser.

No. OctoCounts supports public GitHub repositories only. It does not request GitHub account access, does not support private repositories, and does not accept source-code uploads. For private repositories, the site recommends running tokei locally.

No. The OctoCounts API requires no GitHub account access, no API token, and no sign-up. It analyzes public github.com repositories only, does not support private repositories, and does not accept source-code uploads.

POST to https://api.octocounts.com/api/analyze with a JSON body containing repoUrl and optionally refName, forceRefresh, source, and analysis options. refName may be a branch, tag, or commit SHA; if omitted, OctoCounts uses the repository default branch.

Poll GET https://api.octocounts.com/api/jobs/:jobId. Jobs return queued, running, completed, or failed, and completed jobs include a reportId that you pass to the report endpoint.