jspecify/jspecify

jspecify/jspecify has 8,468 source lines of code out of 16,270 total lines across 233 files, counted with tokei from the main ref at commit 8935b4f21837 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

As of 2026-11-16 (commit 8935b4f21837), jspecify/jspecify contains 16,270 total lines: 8,468 code, 5,463 comments, 2,339 blank, across 233 files in 4 languages (top language: Java 97.9%). Canonical public options (tests, docs and generated files excluded). Counted with tokei via OctoCounts.

As of 2026-11-16 (commit 8935b4f21837), jspecify/jspecify contains 16,270 total lines: 8,468 code, 5,463 comments, 2,339 blank, across 233 files in 4 languages (top language: Java 97.9%). Canonical public options (tests, docs and generated files excluded). Counted with tokei via OctoCounts.

OctoCounts produced this report by resolving jspecify/jspecify to commit 8935b4f21837, downloading the repository source archive, and counting files selected by the effective rules with tokei, the open-source line counter written in Rust. The table below breaks the count down by programming language into files, total lines, code lines, comment lines, and blank lines, so the figures can be compared across languages and projects. Results are cached by commit, tokei version, and analysis options; an exact reproduction needs the same commit, engine version, and effective counting rules.

Repository size insights

This is a small codebase by counted code lines. Code represents 52.0% of all lines, comments represent 33.6%, and the repository averages 36 code lines per file. Java accounts for 97.9% of counted code.

LanguageFilesLinesCodeCommentsBlanks
Java22815690829251672231
Shell124810311926
Batch1112732019
Markdown3220015763

Top language: Java 97.9%. Generated on .

Counting rules and retention

jspecify/jspecify: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

Saved reports remain subject to cache cleanup and replacement. Export the JSON or text for durable citation; live repository URLs can change.

Reproduce this report

Reproduce this exact report and configuration.

Report FAQ

How many lines of code does jspecify/jspecify have?

jspecify/jspecify has 8,468 lines of code, plus 5,463 comment lines and 2,339 blank lines, for 16,270 total lines at commit 8935b4f21837 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

How was the jspecify/jspecify line count measured?

OctoCounts resolved the public GitHub repository to commit 8935b4f21837, downloaded the source archive, counted it with tokei, and cached the report by commit, tokei version, and analysis options.

What commit was counted for jspecify/jspecify?

This OctoCounts report was generated from main at commit 8935b4f21837 on November 16, 2026.

Play the growth animation for jspecify/jspecify on this page — 8,468 code lines across 4 languages, counted by tokei.