pickfit

BrowseDeveloper CLIs

scc

Command-line code counter that reports lines, blanks, comments and code per language, with complexity, ULOC and COCOMO cost estimates.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: go>=1.25 (for go install)

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. Download the scc_Linux_x86_64 release tarball and install the binary to ~/.local/bin

    mkdir -p ~/.local/bin /tmp/scc && curl -fsSL https://github.com/boyter/scc/releases/latest/download/scc_Linux_x86_64.tar.gz -o /tmp/scc/scc.tar.gz && tar xzf /tmp/scc/scc.tar.gz -C /tmp/scc && install -m755 /tmp/scc/scc ~/.local/bin/scc
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

mkdir -p ~/.local/bin /tmp/scc && curl -fsSL https://github.com/boyter/scc/releases/latest/download/scc_Linux_x86_64.tar.gz -o /tmp/scc/scc.tar.gz && tar xzf /tmp/scc/scc.tar.gz -C /tmp/scc && install -m755 /tmp/scc/scc ~/.local/bin/scc
scc --version
mkdir -p /home/sbx/work/sample && cat > /home/sbx/work/sample/main.py <<'EOF'
# a comment
import sys


def f(x):
    if x > 1:
        return 1
    for i in range(3):
        print(i)
    return 0
EOF
cat > /home/sbx/work/sample/dup.py <<'EOF'
# a comment
import sys

def g():
    return 0
EOF
cd /home/sbx/work/sample && scc

Check that it works

scc --version

The output should contain “scc version 4.1.0”.

First thing to try

mkdir -p "$HOME"/work/sample && cat > "$HOME"/work/sample/main.py <<'EOF'
# a comment
import sys


def f(x):
    if x > 1:
        return 1
    for i in range(3):
        print(i)
    return 0
EOF
cat > "$HOME"/work/sample/dup.py <<'EOF'
# a comment
import sys

def g():
    return 0
EOF
cd "$HOME"/work/sample && scc

Change into a project folder and run scc to see line counts per language.

What it does

  • Count code, comment and blank lines
    How to use it
    1. Change into your project folder and run scc to see lines, blanks, comments and code per language.
    2. Run scc --by-file to see the counts for each file.
    Tested
  • Estimate code complexity
    How to use it
    1. Run scc in your project folder and read the Complexity column.
    2. Run scc --by-file to see complexity for each file.
    Tested
  • Get COCOMO and LOCOMO cost estimates
    How to use it
    1. Run scc --cost-comparison in your project folder to see the cost estimates, including the LOCOMO LLM estimate.
    Tested
  • Count unique lines of code (ULOC)
    How to use it
    1. Run scc -u in your project folder and read the Unique Lines of Code (ULOC) line.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 4 of 4 features work
  4. Works offline

Windows and macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • count lines of code per language in a directory
  • estimate development cost of a codebase with COCOMO
  • export code statistics as CSV or JSON for further processing
  • generate an HTML infographic report of a repository

An alternative to cloc, SLOCCount and tokei.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 4.1.0

Differences the test machine hit

  • README: go install github.com/boyter/scc/v4@latest (or sudo snap / dnf / pkg)
    In the test: No Go toolchain and no root in the box, so the README's 'Manual' release binary was used: https://github.com/boyter/scc/releases/latest/download/scc_Linux_x86_64.tar.gz
  • README: Release binary install
    In the test: The prebuilt binary was not inspected (it is opaque)

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.