JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.2p0 | CONFIDENTIAL | CodeSecure Inc |
The following requirements and guidelines should be followed to get the best performance from CodeSonar.
| Windows 11 | |
| Windows 10 | |
| Windows Server 2022 | |
| Windows Server 2019 | |
| Windows Server 2016 |
CodeSonar Java analysis is available on 64-bit Windows and Linux only.
CodeSonar C# analysis is available on 64-bit Windows only, and .NET Framework 4.7.2 or later must be installed on the machine performing the analysis.
The following recommendations reflect the range of browsers that are most rigorously tested with the CodeSonar Web GUI. Since the GUI is designed for portability, many other browsers also work well.
There are some issues to note when opening the CodeSonar manual from disk in certain browsers. See the FAQ for details.
The majority of commonly-used browsers do not readily support in-browser generation and storage of user certificates. To use certificate-based user authentication with such browsers, see the additional material in section Manually Generating and Uploading User Certificates.
CPU and disk requirements for a machine running CodeSonar will depend on whether the machine is used to build and analyze projects or to run a hub.
For a machine that will be running the CodeSonar build/analysis and sending the results to an external hub, the minimum requirements are as follows.
If you want to run the analysis in parallel mode, you will need a minimum of one core and 512MB memory for each process, plus an additional 512MB for the master process. Run the CodeSonar analysis with ANALYSIS_SLAVES=Auto and DAEMON_SLAVES=Auto to have CodeSonar compute how many slaves to run based on your machine's resources.
For a machine that will be running a CodeSonar hub, memory and disk requirements will vary according to the size of the projects analyzed and the frequency of analysis. Some example usage cases and their corresponding requirements are provided below; contact CodeSecure if you need assistance in determining memory and disk requirements for your analysis needs.
The hub database must be stored on a local disk (not a network drive).
Example 1: For a single project with fewer than 500,000 lines of code, where analyses are performed rarely or old analysis results are frequently removed.
Example 2: For a single project with 500,000 lines of code and nightly automated builds; past analyses never removed.
Example 3: For a project or projects totaling 2 million lines of code, with continuous integration and 30 developers.
CodeSonar ships with built-in analysis capability for languages in tier 1 (C, C++) and tier 2 (Java, C#).
| C | CodeSonar parses and generates internal representation for
all features from C89/C90, C99, C11, and most features from
C17/18: for more information, see C Support. Additionally, CodeSonar supports many compiler-specific C language features. See the compiler model documentation for details. |
|---|---|
| C++ | CodeSonar parses and generates internal representation for
all features from C++98, C++11, C++14, and C++17; and most
features from C++20. It also supports some features from C++23.
For more information, see C++ Support. Additionally, CodeSonar supports many compiler-specific C++ language features. See the compiler model documentation for details. |
| Java | The CodeSonar Java analysis is suitable for
Java source and binaries targeting the following.
For more information, see Java Support. CodeSonar ships with its own JVM, so the analysis of Java projects is not dependent on your local Java version(s). |
| C# | The CodeSonar C# analysis is suitable for analyzing the
following .NET versions.
CodeSonar supports C# up to version 10.0. |
Analysis for tier 3 source languages is provided through integration with third-party analyzers.
We provide general instructions for integrating SARIF results from any analyzer with your CodeSonar project. We also provide tool-specific instructions for a select number of third-party analyzers. Some of these are shipped with CodeSonar and some are not.
Analyses performed using older CodeSonar versions may submit results to newer hubs. Specifically, CodeSonar 5.3p0 through 9.2p0 analyses may submit results to CodeSonar 9.2p0 hubs. When using older analysis versions, some GUI functionality may be unavailable for the older analyses.
Analyses performed using newer CodeSonar versions may not submit results to older hubs. Specifically, CodeSonar 9.2p0 analyses require a CodeSonar 9.2p0 hub. Hubs using future versions of CodeSonar may also suffice; consult future versions of this documentation for details.
CodeSonar provides a number of integrations with external third-party software: software that is neither part of CodeSonar nor shipped with CodeSonar.
The following table lists external third-party tools, as well as links to installation instructions and help information.
| CodeSonar Eclipse Plug-in | The Eclipse plug-in has an additional set of prerequisites. |
|---|---|
| CodeSonar Visual Studio Plug-in | The Visual Studio plug-in has an additional set of prerequisites. |
| Bitdefender™ | CodeSonar will not be able to communicate with an HTTP hub on
systems with Bitdefender installed, even if Bitdefender is
disabled. You can work around this by configuring your hub to use HTTPS. |
| ALYac Internet Security Pro | CodeSonar is not compatible with ALYac Internet Security Pro. |
| Avast Antivirus | CodeSonar is not compatible with Avast Antivirus. |
| F-Secure Ultralight Hoster | CodeSonar is not compatible with F-Secure Ultralight Hoster. |
To report problems with this documentation, please visit https://support.codesecure.com/.