RepoPilot

boyter/scc

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

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

dependency CVE scan unavailable

  • ✓Last commit 3d ago
  • ✓18 active contributors
  • ✓Distributed ownership (top contributor 45% of recent commits)
  • ✓MIT licensed
  • ✓CI configured
  • ✓Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: boyter/scc

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T10:00:52.443Z · commit 460a6e8424f7

Verdict

Healthy — Strong maintenance signals

  • Last commit 3d ago
  • 18 active contributors
  • Distributed ownership (top contributor 45% of recent commits)
  • MIT licensed
  • 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

scc is a high-performance Go-based code counter that analyzes source code to compute lines of code (LOC), blank lines, comments, and physical lines across 100+ languages. Unlike cloc or sloccount, it uniquely combines speed, COCOMO cost estimation, cyclomatic complexity calculation, and ULOC (unique lines of code) metrics for DRYness analysis—all in a single CLI tool. Flat monolith with cmd/badges/ as a secondary tool. Core logic resides in the root directory with main package files, language definitions, and counter logic. The ./examples/ directory contains test fixtures (complexity/, duplicates/, countas/, generated/). CI/CD configs in .github/workflows/ and deployment via…

Start here

Open these first:

  • cmd/badges/main.go — Entry point for the scc command-line tool; implements the core CLI interface and orchestrates the code counting workflow
  • .goreleaser.yml — Release and build configuration; essential for understanding how binaries are compiled, versioned, and distributed across…
  • LANGUAGES.md — Comprehensive language definitions and syntax rules; every contributor adding language support must understand this mapping
  • .github/workflows/go.yml — CI/CD pipeline configuration; defines test, build, and quality gates that all PRs must pass
  • go.mod — Dependency manifest; lists all critical libraries including Cobra (CLI), json-iterator (performance), and text processing…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/boyter/scc.git && cd scc && go install ./cmd/scc && scc . (or go run ./cmd/scc/main.go for the main tool; cmd/badges/ is a separate tool for generating badge output)

Daily commands:

go run ./cmd/scc . (default counts current directory) or scc <path> after installation. Key flags visible in Cobra setup: --format (json/csv/html), --complexity, --cocomo, --duplicates, --exclude-dir, --skip-generated.

Key cautions & unknowns

  • No hidden env vars or service dependencies. One non-obvious detail: .ignore and .sccignore are both supported (see .sccignore in repo root), with specific precedence rules not visible in file list—check CONTRIBUTING.md…
  • Published-advisory coverage was unavailable for the captured dependencies.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Healthy" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Healthy
[![RepoPilot: Healthy](https://repopilot.app/api/badge/boyter/scc)](https://repopilot.app/r/boyter/scc)

Paste at the top of your README.md — renders inline like a shields.io badge.

▸Preview social card

This card auto-renders when someone shares https://repopilot.app/r/boyter/scc on X, Slack, or LinkedIn.

Ask AI about boyter/scc

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question

Similar Go repos

Other healthy-signal Go repos by stars.

Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/boyter/scc"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>