C++ Code Analyzer
Paste a public GitHub URL and REPO-SIGHT reads your C++ source directly — complexity, nesting depth, manual memory-management patterns, and 15 rules built specifically for C++. Free.
What REPO-SIGHT checks in your C++ code
15 rules, tuned for C++ — 6 of them security-specific.
Complexity & structure
Cyclomatic complexity, max nesting depth (flagged past 6 levels), and functions over 100 lines — the same thresholds used in the health score.
Manual memory management
cpp-raw-new-delete flags direct new/delete where RAII or a smart pointer would remove a whole class of leaks.
Broad exception handling
cpp-catch-all-ellipsis flags catch (...) blocks that swallow every exception, including ones you didn't expect.
Magic numbers & namespace pollution
cpp-magic-number-literal and cpp-using-namespace-std-header catch two habits that make headers harder to reuse.
Security hotspots
Hardcoded secrets, system()/popen() calls, unsafe buffer functions, weak hashes, and weak random — 6 checks in total.
Duplication & debt
Token-based clone detection across the whole repo, plus every TODO/FIXME counted — cpp-todo-without-ticket flags the ones with no ticket reference.
try {
parseConfig(path);
} catch (...) {
// ignored
}
Illustrative example. cpp-catch-all-ellipsis: this swallows every exception, including ones from unrelated code paths — a specific catch clause (or at least a log line) makes failures visible instead of silent.
Frequently asked questions
Does REPO-SIGHT compile my C++ code?
No. It's a static analyzer — a real lexer and parser walk the source, but nothing is compiled or executed. That's also what makes it safe to run against any public repo.
Which C++ standard does it support?
The parser handles standard C++ syntax — classes, templates, namespaces — without gating on a specific standard version. It's a metrics and rules engine, not a full compiler front-end, so unusually macro-heavy preprocessor tricks can occasionally trip up any static parser, C++'s included.
How is this different from clang-tidy or cppcheck?
Those need a local install and a build/compile setup. REPO-SIGHT runs from a GitHub URL alone, in your browser, in seconds, and rolls everything into a single project health score instead of a raw diagnostic list.
Is my code stored?
Scan results are stored so you can revisit the report link. See the privacy policy for specifics, including what changes if you sign in.
Is it actually free?
Yes — no tiers, no paywalled metrics. A small amount of advertising covers hosting instead of a paid plan.
Other languages
Related reading
Scan a repository in seconds.
No tiers and no paywalled metrics; a small amount of advertising pays for hosting. Sign-in is optional for public repositories and required for private ones.