FREE · NO SIGNUP · RESULTS IN SECONDSIDENTIFIER

The audit you skip when you're solo — done in seconds.

Paste a public GitHub URL and REPO-SIGHT reads the source straight from the repo — size, structure, complexity, technical debt, and rule violations, across C++, Python, and Java.

Public repositories only · best for repos that analyze in under a minute · no account needed

cma . --json report.json

====================================
CODE METRICS REPORT
====================================
Files Analyzed        : 14
Total Lines            : 2,850
Functions              : 65
Classes                : 12
Cyclomatic Complexity  : 137
Longest Function       : processOrder() · 78 lines
TODO Comments          : 9
====================================

THE PIPELINEPREPROCESSOR

Five stages. One pass. No black box.

Every file goes through the same deterministic pipeline — the same one the cma binary runs on the command line.

Scan

Finds every recognized source file — .cpp/.h, .py, .java — in a repo, a folder, or a single file.

Lex

Character-level tokenizer per language. Keywords, identifiers, literals, operators — no regex, no compiler.

Parse

Walks the token stream to find functions, classes, nesting depth, and cyclomatic complexity.

Aggregate

Per-file metrics and rule violations roll up into one project-level report and health score.

Report

A dashboard you can read — never a black box.

WHAT YOU GETSTRING_LITERAL

Every metric the engine computes — one dashboard.

Size & shape

Total lines, blank lines, comment lines, and real code lines — split out, not lumped together.

Structure

Functions, classes/structs, variables, and include/import counts, rolled up project-wide.

Complexity

Cyclomatic complexity, max nesting depth, loops and conditions, and your longest function.

Technical debt

Every TODO and FIXME marker, counted — so nothing quietly rots in a comment.

Rule violations

21 rules across C++, Python, and Java flag risky patterns, rolled up by severity.

LEARNDOC_COMMENT

Read up on what the numbers mean.

Short, practical explainers on the metrics REPO-SIGHT reports and why they matter.

What is static code analysis?

How reading source without running it catches structural problems early — and where it falls short.

Cyclomatic complexity, explained

What the number counts, why 10+ is a common warning line, and how to bring a function back down.

How to read a code health score

What REPO-SIGHT's A–F grade weighs, and what to fix first when a repo grades low.

FREE, FOR NOW AND FOR REAL

Free is the whole plan.

No tiers, no paywalled metrics. A small amount of advertising keeps it free instead of a paywall — analyze without an account any time.

Analyze a repo now

Starting analysis…

—

GRADE —

Code Health

Weighted from complexity density, avg function length, comment ratio, TODO density, and nesting depth.

Functions

—

Cyclomatic

—

TODOs

—

Max Nesting

—

Size & shape

—Total lines

—Code lines

—Comment lines

—Blank lines

Structure

—Classes

—Variables

—Includes / imports

Complexity detail

—Loops

—Conditions

—Try/catch blocks

Longest function

—

flagged at 100 lines (long-function rule)

Start analyzing to build your streak!

The audit you skip when you're solo — done in seconds.

Five stages. One pass. No black box.

Scan

Lex

Parse

Aggregate

Report

Every metric the engine computes — one dashboard.

Size & shape

Structure

Complexity

Technical debt

Rule violations

Read up on what the numbers mean.

What is static code analysis?

Cyclomatic complexity, explained

How to read a code health score

Free is the whole plan.

Overview