# exploitbench/exploitbench SLOC report

> As of 2026-10-06 (commit c0b8a4d0aa52), exploitbench/exploitbench contains 26,964 total lines: 19,868 code, 3,910 comments, 3,186 blank, across 135 files in 13 languages (top: Python 79.9%). Custom configuration (tests excluded, docs excluded, generated excluded). Counted with tokei via OctoCounts.

exploitbench/exploitbench has 19,868 source lines of code out of 26,964 total lines across 135 files, counted from the c0b8a4d0aa5227ac86102dc304e8eb7edbae17bc ref at commit c0b8a4d0aa52 by the OctoCounts tokei engine on 2026-10-06. The report is cached by commit, tokei version, and analysis options, so recounting the same revision returns exactly these numbers.

OctoCounts produced this report by resolving exploitbench/exploitbench to commit c0b8a4d0aa52, downloading the repository source archive, and counting every source file 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, so counting the same revision again reproduces exactly these numbers.

## Repository size insights

This is a medium-sized codebase by counted code lines. Code represents 73.7% of all lines, comments represent 14.5%, and the repository averages 147 code lines per file. Python accounts for 79.9% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| Python | 82 | 19,528 | 15,868 | 1,508 | 2,152 |
| Go | 20 | 3,047 | 2,166 | 532 | 349 |
| C++ | 1 | 819 | 699 | 13 | 107 |
| YAML | 3 | 555 | 288 | 235 | 32 |
| Shell | 5 | 476 | 285 | 127 | 64 |
| JSON | 1 | 180 | 180 | 0 | 0 |
| Makefile | 3 | 197 | 146 | 12 | 39 |
| TOML | 2 | 146 | 90 | 40 | 16 |
| C | 5 | 122 | 81 | 26 | 15 |
| C Header | 1 | 52 | 38 | 3 | 11 |
| Dockerfile | 1 | 41 | 27 | 6 | 8 |
| Markdown | 10 | 1,796 | 0 | 1,403 | 393 |

Top language (Python 79.9%). Generated at 2026-10-06T00:23:36.849318896+00:00. Canonical report: https://octocounts.com/github/exploitbench/exploitbench

## Reproduce this report

[Reproduce this exact report and configuration](https://octocounts.com/github/exploitbench/exploitbench/commit/c0b8a4d0aa5227ac86102dc304e8eb7edbae17bc?analysis=%7B%22ignoredDirs%22%3A%5B%5D%2C%22ignoredLanguages%22%3A%5B%5D%2C%22profile%22%3A%22default%22%2C%22includeDocs%22%3Afalse%2C%22includeTests%22%3Afalse%2C%22includeGenerated%22%3Afalse%7D&reportId=eeeb4c972307d0502635de351da3795def46c7c3743bb0a70522b1c4fe7f598a).

## Report FAQ

### How many lines of code does exploitbench/exploitbench have?

exploitbench/exploitbench has 26,964 total lines, including 19,868 code lines, 3,910 comment lines, and 3,186 blank lines.

### How was the exploitbench/exploitbench line count measured?

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

### What commit was counted for exploitbench/exploitbench?

This OctoCounts report was generated from c0b8a4d0aa5227ac86102dc304e8eb7edbae17bc at commit c0b8a4d0aa52 on 2026-10-06T00:23:36.849318896+00:00.

## Similar repository reports

- [tw93/waza](https://octocounts.com/github/tw93/waza) — Python, 19,918 code lines
- [soundthing/Soundscape](https://octocounts.com/github/soundthing/Soundscape) — Python, 20,029 code lines
- [yuval-harpaz/alarms](https://octocounts.com/github/yuval-harpaz/alarms) — Python, 19,671 code lines
- [sanneel/dropos](https://octocounts.com/github/sanneel/dropos) — Python, 20,075 code lines
- [GaimsDevSoftware/linuxpop](https://octocounts.com/github/GaimsDevSoftware/linuxpop) — Python, 20,165 code lines
- [lewbei/prime-agent-plan](https://octocounts.com/github/lewbei/prime-agent-plan) — Python, 19,499 code lines

## Related OctoCounts pages

- [Recently analyzed repositories](https://octocounts.com/recent)
- [Popular SLOC reports](https://octocounts.com/popular)
- [Trending GitHub repositories](https://octocounts.com/trending)
- [Hall of Monoliths](https://octocounts.com/hall-of-monoliths)
- [TensorFlow vs PyTorch](https://octocounts.com/compare/tensorflow-vs-pytorch)
- [Django vs Ruby on Rails](https://octocounts.com/compare/django-vs-rails)
- [Laravel vs Django](https://octocounts.com/compare/laravel-vs-django)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [SLOC and code metrics glossary](https://octocounts.com/docs/glossary)
- [Original research: how filtering changes SLOC counts](https://octocounts.com/research)
- [OctoCounts API docs](https://octocounts.com/docs/api)