pickfit

BrowseDeveloper CLIs

Tokei

Command-line program that counts files, lines, code, comments and blanks in source code, grouped by language.

Tested on Linux

Use it

Linux x86_64

  1. Download v12.1.2 x86_64-unknown-linux-musl release tarball and extract tokei into ~/.local/bin

    mkdir -p ~/.local/bin /tmp/tk && curl -fsSL -o /tmp/tk/tokei.tar.gz https://github.com/XAMPPRocky/tokei/releases/download/v12.1.2/tokei-x86_64-unknown-linux-musl.tar.gz && tar -xzf /tmp/tk/tokei.tar.gz -C ~/.local/bin
Where the README and reality differ
  • README: You can download prebuilt binaries in the releases section
    What worked: Releases v13.0.0 onward (latest v15.0.0) have no binary assets; the newest prebuilt Linux binary is v12.1.2, so the binary path gives an older version than cargo would

Check that it works

tokei --version

The output should contain “tokei 12.1.2 compiled with serialization support: json, cbor, yaml”.

First thing to try

mkdir -p foo && cat > foo/main.rs <<'EOF'
// line comment
/* outer /* nested */ still comment */
fn main() {

    let s = "/* not a comment */";
    println!("{}", s); // trailing
}
EOF
cat > foo/app.py <<'EOF'
# comment
def f():

    return 1
EOF
tokei ./foo

Run tokei <directory> to see a table of files, lines, code, comments and blanks for each language in that folder.

What it does

  • Count code, comments and blanks by language
    How to use it
    1. Run tokei <directory> on your project folder.
    2. Read the table: one row per language with files, lines, code, comments and blanks.
    Tested
  • Export statistics as CBOR, JSON or YAML
    How to use it
    1. Run tokei <directory> --output json to get the statistics as JSON.
    2. Run tokei <directory> --output yaml to get the statistics as YAML, including per-file entries.
    Tested
  • Count nested and multi-line comments correctly
    Not shown working
  • Use Tokei as a library in your own projects
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • count lines of code per language in a project directory
  • export code statistics as JSON for other programs
  • show per-file code statistics

An alternative to cloc.

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 tokei 12.1.2 compiled with serialization support: json, cbor

Differences the test machine hit

  • README: Install via cargo install tokei, or a distro package manager (apk/pacman/dnf)
    In the test: No Rust toolchain or root here; used the prebuilt release binary (README 'Manual > Downloading')

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.