boyter/scc

Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 7th, 2026
Created on March 1st, 2018
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 345
Total Stargazers: 8,729 (+0)
Total Subscribers: 36 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 679 days
Stale 30+ days: 13
Stale 90+ days: 10

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (32)
  • bug (17)
  • help wanted (5)
  • good first issue (2)

Detailed Description

scc is a command-line code counter that analyzes lines of code, blank lines, comments, and physical lines across many programming languages.

The tool addresses the need to quickly and accurately measure code metrics across large codebases. It counts source lines of code similar to cloc and sloccount but adds several analytical layers: it calculates cyclomatic complexity estimates, produces COCOMO estimates for project cost forecasting, computes LOCOMO estimation for LLM-based development costs, and measures code uniqueness through DRYness metrics. The tool is written in pure Go and emphasizes speed as a core design goal. It supports configuration files, generates HTML reports, offers multiple output formats, and includes a Git insight mode for analyzing repository history. An MCP server mode is available for integration with other tools.

Developers should choose this tool if they need fast, multi-metric code analysis in a single command rather than chaining multiple specialized tools. It suits projects where understanding code complexity, estimating development costs, and tracking code duplication matter alongside basic line counts. The README positions it as an alternative to cloc, sloccount, and tokei, with the distinguishing factors being its speed, the breadth of metrics it produces simultaneously, and its ability to estimate both traditional COCOMO costs and modern LLM-based development expenses.

The project maintains active development with regular updates and improvements to language support. The tool has been adopted in production at searchcode.com for structured code intelligence analysis. The maintainer actively accepts contributions for adding or modifying language definitions, and the codebase includes comprehensive documentation for extending language support.