{"id":14991172,"url":"https://github.com/ericsson/codechecker","last_synced_at":"2026-02-13T15:14:23.384Z","repository":{"id":37431651,"uuid":"37459110","full_name":"Ericsson/codechecker","owner":"Ericsson","description":"CodeChecker is an analyzer tooling, defect database and viewer extension for static and dynamic analyzer tools.","archived":false,"fork":false,"pushed_at":"2025-05-07T08:39:45.000Z","size":43559,"stargazers_count":2385,"open_issues_count":460,"forks_count":408,"subscribers_count":52,"default_branch":"master","last_synced_at":"2025-05-07T09:43:20.556Z","etag":null,"topics":["analysis","c","clang","clang-tidy","codechecker","cpp","database","defects","docker","linux","llvm","macosx","objective-c","results-viewer","static-analysis","static-analyzer","static-analyzers","vue"],"latest_commit_sha":null,"homepage":"https://codechecker.readthedocs.io","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Ericsson.png","metadata":{"files":{"readme":"docs/README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE.TXT","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":"docs/supported_code_analyzers.md","governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2015-06-15T10:38:51.000Z","updated_at":"2025-05-07T08:39:50.000Z","dependencies_parsed_at":"2023-09-29T11:42:30.441Z","dependency_job_id":"50b5428a-2bdc-4def-b0a6-a46baec9079d","html_url":"https://github.com/Ericsson/codechecker","commit_stats":{"total_commits":3749,"total_committers":127,"mean_commits":"29.519685039370078","dds":0.6054947986129635,"last_synced_commit":"4234fb7b91d07681ee032862fbb096197d5f104a"},"previous_names":[],"tags_count":87,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Ericsson%2Fcodechecker","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Ericsson%2Fcodechecker/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Ericsson%2Fcodechecker/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Ericsson%2Fcodechecker/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Ericsson","download_url":"https://codeload.github.com/Ericsson/codechecker/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253747080,"owners_count":21957687,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["analysis","c","clang","clang-tidy","codechecker","cpp","database","defects","docker","linux","llvm","macosx","objective-c","results-viewer","static-analysis","static-analyzer","static-analyzers","vue"],"created_at":"2024-09-24T14:21:38.908Z","updated_at":"2026-02-13T15:14:23.373Z","avatar_url":"https://github.com/Ericsson.png","language":"Python","readme":"\u003ch1 align=\"center\"\u003e\n  \u003cbr\u003e\n  \u003cimg src=\"https://github.com/Ericsson/codechecker/raw/master/docs/logo/logo_blue.png\" alt=\"CodeChecker\" width=\"200\"\u003e\n  \u003cbr\u003e\n  CodeChecker\n  \u003cbr\u003e\n\u003c/h1\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"https://github.com/Ericsson/codechecker/actions\"\u003e\n    \u003cimg src=\"https://github.com/Ericsson/codechecker/workflows/codechecker-tests/badge.svg\"\n         alt=\"Github Action\"\u003e\n  \u003c/a\u003e\n  \u003ca href=\"https://gitter.im/codecheckerHQ/Lobby?utm_source=share-link\u0026utm_medium=link\u0026utm_campaign=share-link\"\u003e\n    \u003cimg src=\"https://badges.gitter.im/codecheckerHQ/Lobby.svg\"\n         alt=\"Gitter\"\u003e\n  \u003c/a\u003e\n  \u003ca href=\"https://codechecker.readthedocs.io/en/latest/?badge=latest\"\u003e\n    \u003cimg src=\"https://readthedocs.org/projects/codechecker/badge/?version=latest\"\n         alt=\"Documentation Status\"\u003e\n  \u003c/a\u003e\n  \u003ca href=\"https://securityscorecards.dev/viewer/?uri=github.com/Ericsson/codechecker\"\u003e\n    \u003cimg src=\"https://api.securityscorecards.dev/projects/github.com/Ericsson/codechecker/badge\"\n         alt=\"OpenSSF Scorecard Score\"\u003e\n  \u003c/a\u003e\n\u003c/p\u003e\n\n**CodeChecker** is a static analysis infrastructure built on the [LLVM/Clang\nStatic Analyzer](http://clang-analyzer.llvm.org) toolchain, replacing\n[`scan-build`](http://clang-analyzer.llvm.org/scan-build.html) in a Linux or\nmacOS (OS X) development environment.\n\n![Web interface showing list of analysed projects and bugs](images/demo.gif)\n\n**Check out our [DEMO](https://codechecker-demo.eastus.cloudapp.azure.com) showing some analysis results of open-source projects!**\n\n# Main features\n## Command line C/C++ Analysis\n  * Executes [_Clang-Tidy_](http://clang.llvm.org/extra/clang-tidy/), [_Clang Static Analyzer_](http://clang-analyzer.llvm.org/) with Cross-Translation Unit analysis, Statistical Analysis (when checkers are available), [_Cppcheck_](https://cppcheck.sourceforge.io/), [_GCC Static Analyzer_](https://gcc.gnu.org/wiki/StaticAnalyzer) and the [_Facebook Infer Analyzer_](https://fbinfer.com).\n  * Creates the JSON compilation database by wiretapping any build process (e.g., `CodeChecker log -b \"make\"`).\n  * Automatically analyzes GCC cross-compiled projects: detecting GCC or Clang compiler configuration and forming the corresponding clang analyzer invocations.\n  * Incremental analysis: Only the changed files and its dependencies need to be reanalyzed.\n  * False positive suppression with a possibility to add review comments.\n  * Result visualization in command line or in static HTML.\n\n## Web-based report storage\n  * **You can store \u0026 visualize thousands of analysis reports** of many analyzers like\n    Clang Static Analyzer (C/C++), Clang Tidy (C/C++), Facebook Infer (C/C++, Java), Clang Sanitizers (C/C++), Spotbugs (Java), Pylint (Python), Eslint (Javascript) ...\n    For a complete list see [Supported Analyzers](supported_code_analyzers.md)\n  * **Web application** for viewing discovered code defects with a streamlined,\n    easy experience (with PostgreSQL, or SQLite backend).\n  * **Gerrit and GitLab integration** Shows analysis results as [GitLab](gitlab_integration.md) or [Gerrit](jenkins_gerrit_integration.md) reviews.\n  * **Filterable** (defect checker name, severity, source paths, ...) and\n    **comparable** (calculates difference between two analyses of the project,\n    showing which bugs have been fixed and which are newly introduced) result\n    viewing.\n  * **Diff mode:** This shows the list of bugs that have been introduced since your last analyzer\n    execution.\n  * Results can be shared with fellow developers, the **comments** and\n    **review** system helps communication of code defects.\n  * Easily implementable [Thrift](http://thrift.apache.org)-based\n    server-client communication used for storing and querying of discovered\n    defects.\n  * Support for multiple bug visualization frontends, such as the web\n    application, a [command-line tool](usage.md) and an\n    [Eclipse plugin](http://github.com/Ericsson/CodeCheckerEclipsePlugin).\n\n## Command line features\n`CodeChecker` command has many subcommands which can be used for example to\nlog and analyze your projects, print the results or start a web server. For\nfull list see the following table or check the help message of this command\n(`CodeChecker --help`):\n\n| `CodeChecker` subcommand | Description                                                                                   |\n|--------------------------|-----------------------------------------------------------------------------------------------|\n| `analyze`                | Execute the supported code analyzers for the files recorded in a JSON Compilation Database.   |\n| `analyzer-version`       | Print the version of CodeChecker analyzer package that is being used.                         |\n| `analyzers`              | List supported and available analyzers.                                                       |\n| `check`                  | Perform analysis on a project and print results to standard output.                           |\n| `checkers`               | List the checkers available for code analysis.                                                |\n| `cmd`                    | View analysis results on a running server from the command line.                              |\n| `fixit`                  | Apply automatic fixes based on the suggestions of the analyzers.                              |\n| `log`                    | Run a build command, collect the executed compilation commands and store them in a JSON file. |\n| `parse`                  | Print analysis summary and results in a human-readable format.                                |\n| `server`                 | Start and manage the CodeChecker Web server.                                                  |\n| `store`                  | Save analysis results to a database.                                                          |\n| `version`                | Print the version of CodeChecker package that is being used.                                  |\n| `web-version`            | Print the version of CodeChecker server package that is being used.                           |\n\n\n`CodeChecker cmd` subcommand also has many other subcommands which can be used\nto get data (products, runs, results, statistics) from a running CodeChecker\nserver. For full list see the following table or check the help message of this\nsubcommand (`CodeChecker cmd --help`):\n\n| `CodeChecker cmd` subcommand | Description                                                                                       |\n|------------------------------|---------------------------------------------------------------------------------------------------|\n| `runs`                       | List the available analysis runs.                                                                 |\n| `history`                    | Show run history of multiple runs.                                                                |\n| `results`                    | List analysis result (finding) summary for a given run.                                           |\n| `diff`                       | Compare two analysis runs and show the difference.                                                |\n| `sum`                        | Show statistics of checkers.                                                                      |\n| `token`                      | Access subcommands related to configuring personal access tokens managed by a CodeChecker server. |\n| `del`                        | Delete analysis runs.                                                                             |\n| `update`                     | Update an analysis run.                                                                           |\n| `suppress`                   | Manage and import suppressions of reports on a CodeChecker server.                                |\n| `products`                   | Access subcommands related to configuring the products managed by a CodeChecker server.           |\n| `components`                 | Access subcommands related to configuring the source components managed by a CodeChecker server.  |\n| `login`                      | Authenticate into CodeChecker servers that require privileges.                                    |\n| `export`                     | Export comments and review statuses from CodeChecker.                                             |\n| `import`                     | Import comments and review statuses into CodeChecker.                                             |\n\n\n# Usage flow\n![Usage diagram](images/usage_flow.png)\n\n- *Step 1*: `CodeChecker log` runs the given build command and records the\nexecuted compilation steps. These steps are written to an output file\n(Compilation Database) in a JSON format.\n- *Step 2*: `CodeChecker analyze` uses the previously created JSON Compilation\nDatabase to perform an analysis on the project, outputting analysis results in\na machine-readable (plist) format.\n- *Step 3*: In this step, you can do multiple things:\n    - Parse and pretty-print the summary and results from analysis result files\n    (`CodeChecker parse`).\n    - Store the results to a running CodeChecker server (`CodeChecker store`).\n    - Compare two analysis results/runs to show the results that differ between\n    the two (`CodeChecker cmd diff`).\n    - etc.\n\nFor more information how to use CodeChecker see our [user guide](usage.md).\n\n# User documentation\n\n* [Getting started (How-To with examples)](usage.md)\n\n## C/C++ Analysis\n* [Analyzer User guide](analyzer/user_guide.md)\n* [Avoiding or suppressing false positives](analyzer/false_positives.md)\n* [Checker and Static Analyzer configuration](analyzer/checker_and_analyzer_configuration.md)\n* [GCC incompatibilities](analyzer/gcc_incompatibilities.md)\n* [Suppressing false positives](analyzer/user_guide.md#source-code-comments)\n\n## Web based report management\n* [Webserver User Guide](web/user_guide.md)\n* [WEB GUI User Guide](/web/server/vue-cli/src/assets/userguide/userguide.md)\n* [Command line and WEB UI Feature overview](feature_comparison.md)\n* Security configuration\n  * [Configuring Authentication](web/authentication.md)\n  * [Configuring Authorization](web/permissions.md)\n* Deployment\n  * [Deploy server using docker](web/docker.md#deployment)\n* Server Configuration\n  * [Configuring Server Logging](logging.md)\n  * [Setting up multiple CodeChecker repositories in one server](web/products.md)\n* Continuous Integration (CI)\n  * [CodeChecker as a GitHub Action](http://github.com/marketplace/actions/codechecker-static-analysis)\n  * [Setting up CI gating with Gerrit and Jenkins](jenkins_gerrit_integration.md)\n* Database Configuration\n  * [PostgreSQL database backend setup guide](web/postgresql_setup.md)\n  * [CodeChecker server and database schema upgrade guide](web/db_schema_guide.md)\n\n### Storage of reports from analyzer tools\nCodeChecker can be used as a generic tool for visualizing analyzer results.\n\nThe following tools are supported:\n\n| Language       | Analyzer                                                                     |\n|----------------|------------------------------------------------------------------------------|\n| **C/C++**      | [Clang Static Analyzer](https://clang-analyzer.llvm.org/)                    |\n|                | [Clang Tidy](https://clang.llvm.org/extra/clang-tidy/)                       |\n|                | [Clang Sanitizers](supported_code_analyzers.md#clang-sanitizers)             |\n|                | [Cppcheck](/docs/tools/report-converter.md#cppcheck)                         |\n|                | [Facebook Infer](/docs/tools/report-converter.md#facebook-infer)             |\n|                | [Coccinelle](/docs/tools/report-converter.md#coccinelle)                     |\n|                | [Smatch](/docs/tools/report-converter.md#smatch)                             |\n|                | [Kernel-Doc](/docs/tools/report-converter.md#kernel-doc)                     |\n|                | [Sparse](/docs/tools/report-converter.md#sparse)                             |\n|                | [cpplint](/docs/tools/report-converter.md#cpplint)                           |\n| **C#**         | [Roslynator.DotNet.Cli](/docs/tools/report-converter.md#roslynatordotnetcli) |\n| **Java**       | [SpotBugs](/docs/tools/report-converter.md#spotbugs)                         |\n|                | [Facebook Infer](/docs/tools/report-converter.md#facebook-infer)                    |\n| **Python**     | [Pylint](/docs/tools/report-converter.md#pylint)                             |\n|                | [Pyflakes](/docs/tools/report-converter.md#pyflakes)                         |\n| **JavaScript** | [ESLint](/docs/tools/report-converter.md#eslint)                             |\n| **TypeScript** | [TSLint](/docs/tools/report-converter.md#tslint)                             |\n| **Go**         | [Golint](/docs/tools/report-converter.md#golint)                             |\n| **Markdown**   | [Markdownlint](/docs/tools/report-converter.md#markdownlint)                 |\n|                | [Sphinx](/docs/tools/report-converter.md#sphinx)                             |\n\n\nFor details see\n[supported code analyzers](supported_code_analyzers.md) documentation and the\n[Report Converter Tool](/docs/tools/report-converter.md).\n\n## Common Tools\nUseful tools that can also be used outside CodeChecker.\n\n* [Build Logger (to generate JSON Compilation Database from your builds)](/analyzer/tools/build-logger/README.md)\n* [Plist/Sarif to HTML converter (to generate HTML files from the given plist or sarif files)](/docs/tools/report-converter.md#plist-to-html-tool)\n* [Report Converter Tool (to convert analysis results from other analyzers to the codechecker report directory format))](/docs/tools/report-converter.md)\n* [Translation Unit Collector (to collect source files of a translation unit or to get source files which depend on the given header files)](/docs/tools/tu_collector.md)\n* [Report Hash generator (to generate unique hash identifiers for reports)](/docs/tools/report-converter.md#report-hash-generation-module)\n\n## Helper Scripts\n* [Helper Scripts for daily analysis](script_daily.md)\n\n# Install guide\n\n## Install CodeChecker via `pip`\nCodeChecker is available on the [pypi](https://pypi.org/project/codechecker/)\nand can be installed with the following command:\n```sh\npip3 install codechecker\n```\n\n**Note:** this package can be installed on `Linux`, `OSX` and `Windows`\nsystems where `pip3` command is available. On `OSX`, `intercept-build` must be\ninstalled for logging (`CodeChecker log`). On `Windows`, logging is not\navailable.\n\n## Installing CodeChecker via the `snap` package manager\nCodeChecker is available on the [Snap Store](https://snapcraft.io/codechecker)\nand can be installed with the following command:\n```sh\nsudo snap install codechecker --classic\n```\n\n**Note:** Unfortunately, the snap package supports only lower-case command names.\nFor this reason, you need to use `codechecker` command instead of `CodeChecker`\neverywhere. For a full list of available commands in the _codechecker_ snap\npackage, run `snap info codechecker`.\n\n## Linux: Build from source\n\nFor a detailed dependency list, and for instructions on how to install newer\nClang and Clang-Tidy versions, please see [Requirements](deps.md).\nThe following commands are used to bootstrap CodeChecker on Ubuntu 20.04 LTS:\n\n```sh\n# Install mandatory dependencies for a development and analysis environment.\n# NOTE: clang or clang-tidy can be any sufficiently fresh version, and need not\n#       come from package manager!\n#       In case of Cppcheck, the minimal supported version is 1.80.\n#       In case of gcc, the minimal supported version is 13.0.0.\n#       Infer: https://fbinfer.com/docs/getting-started\nsudo apt-get install clang clang-tidy cppcheck g++ build-essential curl \\\n      gcc-multilib git python3-dev python3-venv python3-setuptools\n\n# In case of venv_dev target and Ubuntu 23 Linux, install an additional library:\nsudo apt-get install libpq-dev\n\n# Install nodejs dependency for web. In case of Debian/Ubuntu you can use the\n# following commands. For more information see the official docs:\n# https://nodejs.org/en/download/package-manager/\ncurl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -\nsudo apt-get install -y nodejs\n\n# Check out CodeChecker source code.\ngit clone https://github.com/Ericsson/CodeChecker.git --depth 1 ~/codechecker\ncd ~/codechecker\n\n# Create a Python virtualenv and set it as your environment.\n# NOTE: if you want to develop CodeChecker, use the `venv_dev` target instead\n# of `venv`.\nmake venv\nsource $PWD/venv/bin/activate\n\n# [Optional] If you want to use external authentication methods (LDAP / PAM)\n# follow the instructions in\n# docs/web/authentication.md#external-authentication-methods\n\n# Build and install a CodeChecker package.\nmake package\n\n# For ease of access, add the build directory to PATH.\nexport PATH=\"$PWD/build/CodeChecker/bin:$PATH\"\n\ncd ..\n```\n\n**Notes**:\n- By default, `make package` will build ldlogger shared objects for\n`32bit` and `64bit` too. If you would like to build and package `64 bit only`\nshared objects and ldlogger binary you can set `BUILD_LOGGER_64_BIT_ONLY`\nenvironment variable to `YES` before the package build:\n`BUILD_LOGGER_64_BIT_ONLY=YES make package`.\n- By default, the `make package` will build the UI code if it's not built yet\nor the UI code is changed. If you wouldn't like to build the UI code you can\nset the `BUILD_UI_DIST` environment variable to `NO` before the package build:\n`BUILD_UI_DIST=NO make package`.\n- Use `make standalone_package` instead of `make package` to avoid\nhaving to manually activate the environment before running CodeChecker.\n\n### Minimum Recommended package versions\n\n* In production it is recommended to execute CodeChecker with the minimum Python versions: 3.7.14, 3.8.14, 3.9.14, 3.10.6, 3.11.0, otherwise it may be vulnerable to open-redirect attacks. For more info see https://python-security.readthedocs.io/vuln/http-server-redirection.html (CVE-2021-28861).\n\n### Upgrading environment after system or Python upgrade\n\nIf you have upgraded your system's Python to a newer version (e.g., from\n`3.8` to `3.11` \u0026ndash; this is the case when upgrading Ubuntu from\n20.04 LTS to 22.04 LTS), the installed environment will not work\nout-of-the-box. To fix this issue, run the following command to upgrade your\n`checker_env` too:\n\n```sh\ncd ~/codechecker/venv\npython3 -m venv .\n```\n\n## Mac OS X\nFor installation instructions for Mac OS X see [Mac OS X Installation Guide](install_macosx.md) documentation.\n\n## Docker\nTo run the CodeChecker server in Docker see the [Docker](web/docker.md) documentation.\nYou can find the CodeChecker web-server container at the [Docker Hub](https://hub.docker.com/r/codechecker/codechecker-web).\n\n\u003cimg src=\"https://raw.githubusercontent.com/Ericsson/codechecker/master/docs/images/docker.jpg\" width=\"100\"\u003e\n\n## Visual Studio Code plugin\n\u003cimg src=\"https://raw.githubusercontent.com/Ericsson/codechecker/master/docs/images/vscode.png\" width=\"100\"\u003e\n\nYou can install and use CodeChecker VSCode extension from the\n[Visual Studio Marketplace](http://marketplace.visualstudio.com/items?itemName=codechecker.vscode-codechecker)\nor from [Open VSX](http://open-vsx.org/extension/codechecker/codechecker).\n\nMain features:\n- Run CodeChecker analysis from the editor and see the results automatically.\n- Re-analyze the current file when saved.\n- Commands and build tasks for running CodeChecker as part of a build system.\n- Browse through the found reports and show the reproduction steps directly in the code.\n- Navigate between the reproduction steps.\n\n![VSCode plugin](images/vscode.gif)\n\nFor more information how to install and use this plugin see the\n[repository](https://github.com/Ericsson/codecheckervsCodePlugin/) of this\nextension.\n\n## GitHub Actions CI\n\n![CodeChecker executed in GitHub Actions](images/github-actions.png)\n\nCodeChecker can be executed via a reusable GitHub action for your project!\nYou need only specify the build command, as if you would run the analysis\nlocally.\n\nFor more information, check out the\n[CodeChecker Static Analysis](http://github.com/marketplace/actions/codechecker-static-analysis)\naction on the GitHub Actions Marketplace.\n\n# Analyze your first project\n\n## Setting up the environment in your Terminal\n\nThese steps must always be taken in a new command prompt you wish to execute\nanalysis in.\n\n```sh\nsource ~/codechecker/venv/bin/activate\n\n# Path of CodeChecker package\n# NOTE: SKIP this line if you want to always specify CodeChecker's full path.\nexport PATH=~/codechecker/build/CodeChecker/bin:$PATH\n\n# Path of the built LLVM/Clang\n# NOTE: SKIP this line if clang is available in your PATH as an installed Linux package.\nexport PATH=~/\u003cuser path\u003e/build/bin:$PATH\n```\n## Execute analysis\n\nAnalyze your project with the `check` command:\n\n    CodeChecker check -b \"cd ~/your-project \u0026\u0026 make clean \u0026\u0026 make\" -o ./results\n\n`check` will print an overview of the issues found in your project by the\nanalyzers. The reports will be stored in the `./results` directory in `plist`\nXML format.\n\n## Export the reports as static HTML files\nYou can visualize the results as static HTML by executing\n\n`CodeChecker parse -e html ./results -o ./reports_html`\n\nAn index page will be generated with a list of all repors in\n`./reports_html/index.html`\n\n\n## Optionally store the results in Web server \u0026 view the results\n\nIf you have hundreds of results, you may want to store them on the web\nserver with a database backend.\n\nStart a CodeChecker web and storage server in another terminal or as a\nbackground process. By default, it will listen on `localhost:8001`.\n\nThe SQLite database containing the reports will be placed in your workspace\ndirectory (`~/.codechecker` by default), which can be provided via the `-w`\nflag.\n\n    CodeChecker server\n\nStore your analysis reports onto the server to be able to use the Web Viewer.\n\n    CodeChecker store ./results -n my-project\n\nOpen the [CodeChecker Web Viewer](http://localhost:8001) in your browser, and\nyou should be greeted with a web application showing you the analysis results.\n\n\n## Developer documentations\n* [Architecture](architecture.md)\n* [Package layout](package_layout.md)\n* [Dependencies](deps.md)\n* [Thrift interface](web/api/README.md)\n* [Package and integration tests](tests.md)\n* [Server-side background tasks](web/background_tasks.md)\n\n## Conference papers, presentations\n* An overview about the CodeChecker infrastructure was given at [PLDI 2020](http://pldi20.sigplan.org).\u003cbr /\u003e\n  **Márton, Gábor and Krupp, Dániel**:\u003cbr /\u003e\n  [_Tool Talk: CodeChecker_](http://youtube.com/watch?v=bVqrhaoxHlc)\n* A high-level overview about the infrastructure is available amongst the\n  [2015 Euro LLVM Conference](http://llvm.org/devmtg/2015-04) presentations.\u003cbr/\u003e\n  **Krupp, Dániel and Orbán, György and Horváth, Gábor and Babati, Bence**:\u003cbr/\u003e\n  [_Industrial Experiences with the Clang Static Analysis Toolset_](http://llvm.org/devmtg/2015-04/slides/Clang_static_analysis_toolset_final.pdf)","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fericsson%2Fcodechecker","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fericsson%2Fcodechecker","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fericsson%2Fcodechecker/lists"}