Analyzing the OneX Open‑Source Project with scc: Code Lines, Complexity, and Cost Estimation

When browsing GitHub I found the OneX project and wanted to know its size, so I counted its Go source lines using a simple find . -name "*.go" -print | xargs wc -l | tail -n 1 command, which reported 155,784 lines.

To obtain richer metrics I introduced the scc tool, a fast Go‑written source‑code counter that also computes complexity and COCOMO cost estimates. Installation commands are shown ( go install github.com/boyter/scc/v3@latest or brew install scc ).

Running scc in the project directory produces a table with language, file count, total lines, blank lines, comment lines, code lines, and complexity. The analysis shows Go dominates with 76.5% of lines, a 16.2% overall comment ratio, and an average complexity of about 9.3 per Go file.

Using the built‑in COCOMO model, scc estimates a development cost of $5,124,210, a schedule of 25.59 months, and a team size of roughly 18 people. The cost per thousand lines of code is about $25.16.

The article also compares scc with other tools such as cloc and tokei, highlighting scc’s speed while noting cloc’s broader language support and tokei’s low memory usage but lack of complexity analysis.

A comparison table summarises each tool’s language, core features, advantages, and limitations. Finally, links to the OneX repository, scc, cloc, tokei, and COCOMO documentation are provided along with author contact information.