CLion 2026.1.2 Introduces Built-in SARIF Viewer: Your Questions Answered

The latest CLion update, version 2026.1.2, brings a powerful new feature for static analysis integration: a built-in SARIF Viewer. This tool is designed to streamline workflows for teams relying on external static analysis tools, particularly in embedded and automotive development. Below, we answer common questions about how the viewer works, who benefits from it, and how to get started.

What is the new SARIF Viewer in CLion and why was it added?

The SARIF Viewer is a natively integrated feature in CLion 2026.1.2 that lets you open and interact with Static Analysis Results Interchange Format (SARIF) reports directly inside the IDE. It was added to address a common pain point for development teams: the need to switch between multiple tools to review static analysis findings. Instead of opening a separate web dashboard or proprietary tool, you can now view, navigate, and triage results right next to your code. This integration is especially valuable for teams that must comply with industry standards like MISRA, AUTOSAR, CERT C/C++, or ISO 26262, where external static analysis is a non-negotiable part of the quality process.

How does the SARIF Viewer benefit embedded and automotive teams?

For teams working on safety-critical systems, compliance often means using specialized static analysis tools such as Parasoft C/C++test, Clang Static Analyzer, or proprietary in-house checkers. These tools produce SARIF reports that previously lived in CI artifacts, web dashboards, or vendor-specific interfaces. The SARIF Viewer brings those reports directly into the IDE, allowing developers to review findings alongside the source code, jump to the exact location of an issue, and manage the entire triage process without leaving the development environment. This reduces context switching, improves productivity, and helps maintain a clear audit trail for regulatory requirements.

What exactly is SARIF and why is it important?

SARIF stands for Static Analysis Results Interchange Format. It is a standardized JSON-based format designed to represent analysis results from any static analysis tool. A SARIF file includes information about detected issues, the rules that triggered them, severity levels, code locations, and even execution flows for path-sensitive analyses. This common format is crucial when a project relies on multiple analysis tools (e.g., compiler warnings, C/C++ analyzers, and internal quality gates). Instead of dealing with disparate outputs, teams can consolidate all findings into a single SARIF report and use a compatible viewer—like CLion’s—to review everything in one place. For more details, see how to import reports.

How can you import SARIF reports into CLion?

Importing a SARIF report is straightforward. You have two options: select Code → Import SARIF Results… from the main menu and choose your .sarif or .sarif.json file, or simply drag and drop the file into the IDE’s Project tool window. CLion will validate the file format and automatically add a new SARIF Results tab to the Problems tool window. The findings are grouped by the tool that generated them and by rule, making it easy to focus on specific categories. Once imported, you can double-click any result to open the corresponding source code location in the editor. For more on managing results, see how to triage and filter.

How does the viewer work after importing, and can you manage triage state?

Once a SARIF report is imported, the viewer stores the imported data on a per-project basis. This means that when you close and reopen your project, the triage state is preserved—any findings you’ve marked as acknowledged, suppressed, or reviewed will be retained. You can also clear the current results, re-import an updated report, or apply filters and grouping options from the SARIF Results toolbar. This workflow allows you to treat static analysis findings as part of your ongoing development process, not just a one-time check. If you need to start fresh, simply clear the imported data and re-import a revised report.

Can you disable the SARIF Viewer plugin if not needed?

Absolutely. If your project does not use SARIF reports, you can easily disable the plugin to free up resources. Go to Settings → Plugins → Installed, find SARIF Viewer in the list, and uncheck the box. This disables the feature without uninstalling it permanently. You can re-enable it later whenever you need to import a SARIF file. This is especially useful for teams that occasionally work on compliance-related projects but don’t require the viewer in their everyday workflow.

Where can you get CLion 2026.1.2 to try the SARIF Viewer?

CLion 2026.1.2 is available for download from JetBrains’ official website. The SARIF Viewer comes included out of the box—no separate installation or configuration is required. To try it, simply download and install the update, then import any SARIF 2.1.0-compatible report (from tools like Parasoft, Clang, or your own custom checkers). You can also use sample reports provided in the CLion documentation to test the workflow. If you have feedback or feature requests, the JetBrains team welcomes your input to help improve the viewer in future releases.