HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
XAMPPRocky
tokei
Rust2015–2025
XAMPPRocky / tokei

tokei

Count your code, quickly.

Command LineSystems & InfrastructureScience & EngineeringMobile & Desktop
Explore on GitHubRead Hacker News discussions
25Distinct people
27Mentions
0Explicit recommenders
15.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Count your code, quickly.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year27 dated mentions

Observed mentions: 2015-12-10 19:58:26 UTC to 2025-05-24 17:31:55 UTC.

02462015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC642
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC413
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC321

What Hacker News says

27 sources
NewJazz·May 10, 2025
Out of curiosity I ran toeki a tool for counting lines of code, and found a staggering 3.6 million lines of rust. Removing the vendored packages reduces this to 11136 lines of rust. Tokei hasn't had a stable release in over 4 years and misreports lines of code in some instances. The author in the past has basically said they would need to be paid to backport one line fixes with no merge conflicts that fix real accuracy issues in their software... Bad look in my book. https://github.com/XAMPPRocky/tokei/issues/875
In Rust’s dependencies are starting to worry me
yangrobotics·Aug 26, 2024
I am the author of this toy project. My personal website is [here]((https://yangrobotics.com). Thank you all for your interest! This project began as an effort to mentor a talented high school student in learning Rust and robotics. During the process, I realized that there was a lack of educational materials available online. In response, I set out to create a minimal example of quadrotor control and planning in Rust. I was inspired by [llm.c](https://github.com/karpathy/llm.c), which teaches complex topics with minimal code. My goal was to provide a similar experience, introducing the magic behind quadrotor autonomy with as little code as possible. With the initial framework I developed, I am thrilled to see that my mentee is now able to work independently, experimenting with his own ideas in Rust! I believe this codebase will be valuabl
Read the rest
e for anyone who wants to: a. Learn the principles behind quadrotor autonomy. Code robotics in Rust. b. Explore the challenges of using Rust before incorporating it into their projects. Throughout the development of this project, I have strived to work entirely within the Rust ecosystem. I am now convinced that Rust is ready for serious robotics development. Here are some tools I've been using: 1. [zed.dev](https://yangrobotics.com) for code editing. 2. [Rerun](rerun.io) for visualization. 3. [tokei](https://github.com/XAMPPRocky/tokei) for code line statistics. 4. [nalgebra](https://nalgebra.org) for matrix operations. There are still a few things I'm searching for, such as a robust optimization library. Currently, I'm experimenting with [OpEn](https://alphaville.github.io/optimization-engine) for nonlinear model predictive control, but I hope to find something akin to [acados](https://github.com/acados) in Rust. Additionally, while nalgebra is solid, I believe it still doesn't outperform [Eigen](https://eigen.tuxfamily.org) in terms of performance, though Rust's language features might limit the possibility of implementing something like Eigen. I'm open to suggestions and feedback! For instance, I’m still debating whether to modularize the pipeline and add async features, or whether to keep things simpler to avoid overwhelming beginner learners. Current code statistics: Rust: 1263 Markdown: 305 Comments: 19 Blanks: 44 PS: When naming the project "Peng," I had no idea that "peng" also means attractive! Well, I hope you find the project attractive too.
In Peng – A minimal Rust-based quadrotor simulation pipeline
boyter·Jul 29, 2024
More lines of code usually indicates more bugs so its not an entirely useless metric. Using it to gauge employee productivity is, since as the linked suggests some of the better programmers are able to remove code, which often reduces the potential for bugs. I personally find some use it in, if nothing else to identify which files probably need to be refactored as they are too large, or complex. Throw in some cyclomatic complexity and you are getting some useful information out the code counts. Counting lines of code is one metric though. Another I have seen thrown around is ULOC https://cmcenroe.me/2018/12/14/uloc.html where you count the number of unique lines of code, sort -u *.h *.c | wc -l Again another metric that potentially speaks to the health of a project. I personally wrote about this some time ago when someone asked why I
Read the rest
wrote a code counting project https://boyter.org/posts/why-count-lines-of-code/ and I liked the idea of ULOC so much I integrated it into the project as well. Clearly I am not alone in this though, hence there being so many code counters around (forgive me if I missed yours in the following list) and discussion around it. - [SLOCCount](https://www.dwheeler.com/sloccount/) the original sloc counter - [cloc](https://github.com/AlDanial/cloc), inspired by SLOCCount; implemented in Perl for portability - [gocloc](https://github.com/hhatto/gocloc) a sloc counter in Go inspired by tokei - [loc](https://github.com/cgag/loc) rust implementation similar to tokei but often faster - [loccount](https://gitlab.com/esr/loccount) Go implementation written and maintained by ESR - [ployglot](https://github.com/vmchale/polyglot) ATS sloc counter - [tokei](https://github.com/XAMPPRocky/tokei) fast, accurate and written in rust - [sloc](https://github.com/flosse/sloc) coffeescript code counter - [scc](https://github.com/boyter/scc) my own counter Incidentally the articles author confused me for a while using standard unix tools to count code, as I had them confused for David Wheeler who wrote the very first code counter that I know of sloccount.
In Counting Lines of Code
SushiHippie·Feb 18, 2024
I've run tokei [0] on the Linux git repository on the latest commit [1] and this was the output: =============================================================================== Language Files Lines Code Comments Blanks =============================================================================== C 33553 23772322 17694564 2662642 3415116 C Header 24554 9562920 7395591 1436546 730783 Device Tree 5041 1512839 1240129 76384 196326 ReStructuredText 3473 711669 539971 0 171698 JSON 788 443098 443096 0 2 YAML 3905 433860 352107 16626 65127 GNU Style Assembly
Read the rest
1317 372131 271873 55613 44645 Shell 894 172036 120033 21590 30413 Plain Text 1739 151033 0 123992 27041 Makefile 2946 76889 52985 12355 11549 Python 203 68545 54627 4452 9466 SVG 74 49420 48159 1171 90 Perl 59 43992 34124 4074 5794 Happy 10 6069 5359 0 710 Assembly 5 3319 3065 0 254 C++ 5 2138 1860 61 217 BASH 59 1943 1318 335 290 Unreal Script 5 707 445 158 104 ASN.1 16 660 445 87 128 Autoconf 5 429 373 26 30 LD Script 8 376 288 29 59 CSS 3 295 172 69 54 Gherkin (Cucumber) 1 291 199 58 34 TeX 1 236 156 74 6 XSL 10 200 122 52 26 HEX 2 173 173 0 0 Module-Definition 2 128 113 0 15 C++ Header 2 125 59 55 11 RPM Specfile 1 108 93 1 14 Objective-C 1 89 72 0 17 Vim script 1 42 33 6 3 Markdown 1 36 0 27 9 Automake 3 31 23 3 5 Ruby 1 29 25 0 4 INI 2 13 6 5 2 TOML 1 12 2 9 1 Apache Velocity 1 12 12 0 0 CMake 2 8 8 0 0 ------------------------------------------------------------------------------- Rust 64 12637 9489 1612 1536 |- Markdown 55 8243 808 5557 1878 (Total) 20880 10297 7169 3414 ------------------------------------------------------------------------------- HTML 2 28 22 3 3 |- JavaScript 1 7 7 0 0 (Total) 35 29 3 3 =============================================================================== Total 78760 37400888 28271191 4418115 4711582 =============================================================================== So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05% [0] https://github.com/XAMPPRocky/tokei [1] https://github.com/torvalds/linux/commit/b401b621758e46812da...
In The Linux Kernel Prepares for Rust 1.77 Upgrade

Showing the 15 most recent of 27 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.