REPOSITORY DOSSIER  ·  github.com

boyter/scc

174 files 13 languages 79,694 total lines @e762424 analysed just now

A tool similar t…

01Overview

scc · 65,695 lines of actual code
174
Files
65,695
Code lines
7,605
Comments
13
Languages
7,738
Complexity
0
Secrets
Line Composition 79,694 total lines
Code65,69582.4%
Blank6,3948.0%
Comments7,6059.5%
~99%
tokens saved
Reading boyter/scc via an LLM
~459k tokens ~1.4k tokens via code_analyze

The entire repo summarised by code_analyze — structured JSON in <2k tokens. The dossier above is built from one call. Drill into specifics with code_search.

02Languages & Tech Stack

what it’s written in, what it depends on

Language Breakdown

Language
Files
Code
Share
Go
144
51,221
78.0%
JSON
2
9,296
14.2%
Markdown
7
1,971
3.0%
HTML
2
1,633
2.5%
Go Template
2
633
1.0%
Shell
2
553
0.8%
Python
2
225
0.3%
Powershell
2
46
0.1%
YAML
1
33
0.1%
+ 4 more
62
·

03Notable Files

where complexity and size live

04Code Quality

style, correctness, and maintainability findings

By Severity & Category

Warning
190
Info
274
Error
0
Total
464
By Category
correctness 227 maintainability 95 performance 140 security 2

Top Findings

Blank identifier discarding results; verify intentional ignoring of return values ×3
Declared map variable without initialization; writing to a nil map causes a panic. Use make() to initialize
Ensure errors are handled or logged

05Secrets & Credentials

pattern-based scan for hardcoded secrets
✓   No hardcoded credentials or secret patterns detected. Pattern-based scan only — does not catch logic-level vulnerabilities.

Scan another repository

Drop any public git URL or owner/repo shorthand.

Or compare boyter/scc against another repo:

Or use the API directly: curl https://api.searchcode.com/api/v1/code_analyze  ·  Add to your MCP client