Ericsson/codechecker

CodeChecker is an analyzer tooling, defect database and viewer extension for static and dynamic analyzer tools.

Owned by Ericsson

View on GitHub ↗Jump to charts ↓

Ericsson/codechecker has 2.5k+ stars and 450+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 3 minutes ago
Added to GitGenius on October 10th, 2026
Created on June 15th, 2015
Open Issues & Pull Requests: 317 (+0)
GitHub issues: Enabled
Number of forks: 496
Total Stargazers: 2,629 (+0)
Total Subscribers: 52 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.9 days
Mean response time: 601.8 days
90th percentile: 2362.4 days
Tracked items: 446

Maintainer activity

20 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 18% of issues opened in the past year have never received a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "discussion :bulb:" is answered fastest, typically in about 3 days, while "enhancement :star2:" waits about 18 months. 60% of issues opened in the past year have been closed, leaving a working backlog. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 221
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 1,380 days
Stale 30+ days: 184
Stale 90+ days: 1

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 4

Top labels

  • good to go :rocket: (118)
  • enhancement :star2: (110)
  • analyzer :chart_with_upwards_trend: (102)
  • bug :bug: (83)
  • discussion :bulb: (67)
  • GUI :art: (53)
  • CLI :computer: (52)
  • server :desktop_computer: (51)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

CodeChecker is a static analysis infrastructure built on the LLVM/Clang Static Analyzer toolchain that replaces scan-build in Linux and macOS development environments.

The tool addresses the challenge of running multiple static analyzers across C and C++ codebases and managing their results. It works by executing various analyzers—including Clang-Tidy, Clang Static Analyzer with Cross-Translation Unit analysis, Cppcheck, GCC Static Analyzer, and Facebook Infer—against code. It creates JSON compilation databases by wiretapping build processes, automatically detects and handles GCC cross-compiled projects, and supports incremental analysis so only changed files and their dependencies are reanalyzed. Results can be suppressed with review comments and viewed either from the command line or in static HTML.

Teams working on C and C++ projects should consider CodeChecker if they want to consolidate multiple analyzer tools into a single workflow rather than running each analyzer separately. It suits projects where build integration is straightforward and where teams need a centralized way to track and review static analysis findings across the codebase. The tool provides both command-line and web-based interfaces for result inspection, making it adaptable to different team workflows.

The project maintains active test coverage through continuous integration workflows. Documentation is kept current and accessible through a dedicated documentation site. The codebase shows ongoing maintenance with security scorecard tracking in place.