What is a code issue?

When a system is expected to behave in a certain way and it fails to meet the result, the issue occurs. Similarly, any defect or bug found in the code leads to code issues. Embold helps to identify the code issues in your software and provide the solutions for the same. 

Yes No

Issue Suppression

Code issues are one of the important assets of Embold analysis. Issue suppression is a feature that lists the suppressed code issues within a file/project. Suppression means basically ignoring some parts or a whole parts of the code.

In a few cases, code analysis gives false-positive. Issue suppression is a feature that allows users to suppress these false-positive issue occurrences. This is important because disabling the issue type entirely will not be correct in many cases. If one issue is suppressed, it will be taken off from the code issues panel and will be moved to separate suppressed issues panel.

Steps for suppressing an issue:

1. Go to the Component Explorer present at the top navigation bar next to the duplication tab.
2. Click on the icon on the left side for the issue to be suppressed.
3. Click on Suppress this occurrence” icon.
4. Add comment i.e. the reason for suppression.
5. Click on the Submit button.

Steps for unsuppressing an issue :

  1. Go to the Component Explorer present at the top navigation bar next to the duplication tab.
  2. From the Suppressed Issues tab, click on the unsuppress icon.
Suppression details can be seen on click of suppressed issue .
Yes No

Code checker configuration

Code checker configuration helps you to enable or disable code checkers and their corresponding rules for any repository.

Steps to navigate to code checker configuration
  1. Select the Code checkers configuration option from the repository context menu of the desired repository.
  2. On the Code checkers configuration page, on the left side navigation pane, by default, code issues are enabled except few.
  3. Check or uncheck the radio button to enable or disable a specific rule. If you want the checkers to be disabled, you can disable the code checkers (for example GammaCXX or cppcheck).
  4. For a specific selected checker, rules will be displayed.
  5. Move the cursor on the desired rule to view the More info button. More info will display a detailed description and examples.
  6. Users can search rules manually by typing in the search text box.
  7. On the right side navigation pane, the Filter Rules section can be used to filter the displayed rules based on Criticality or by associated KPI.
  8. To download the file, click Download JSON at the bottom right corner of the code configuration page. This file provides a customized configuration in JSON format and you can change it manually.
  9. To upload the changed file, click Upload JSON Configuration at the top of the code configuration page.
Yes No

Generic Module

The generic module is used to import code issues from a file. Regardless of language or combination of languages, if you get your code issues data into the generic format as specified by this module, it will be imported and correctly applied.

Module Name:


The supported format looks like:

Supported severity types :
Critical, High, Medium, Low and Info


Step 1: There are two ways to get generic code issues:

  1. By specifying the path of the CSV file where it is located:
    To specify a path, use the following API:
    POST - api/v1/repositories/{repositoryUid}/config/{moduleType}/{moduleName}
    Refer to this link to get additional information.
  2. By uploading a zip file: Here, the CSV file is zipped and send to API.
    To upload zip use following API:
    POST - api/v1/repositories/{repositoryUid}/upload/{moduleName}
    Refer to this link to get additional information.
Please refer API documentation to get detailed information on each of these APIs.
Currently, we are supporting this generic module through API only.

Step 2: Run scan to get the generic code issues on UI.

Yes No


The software vulnerability is basically an error or a weakness present in the software code. Those are product-related threats that can hamper your data and gain access to your products and data.

Once, a vulnerability is detected in a code, there is a high risk from a security perspective. External attackers can exploit and trigger the information systems. This may affect the performance of your product.

Vulnerabilities can be caused due to many reasons like design implementation, input validation errors, code injection, complexity in building large systems, and so on.

The most effective way to prevent these vulnerabilities is by enforcing standard security practices. Check here to know more about security standards supported by Embold.

Supported languages

Java: Vulnerabilities in Java can be found and Embold can help in detecting those.

To get more details about the vulnerability count, refer to this table.

Yes No
Suggest Edit