Checkmarx vs. SonarQube for IDE

If you are going with SAST process or want to improve overall security posture then go for it like integrating it with post deployment steps. If you are more concerned about proactive controls better choose other options such as pee-commit hooks and CI security. Also choose other tools for DAST and API scans.

Incentivized

• Supports a large number of languages
• Finds a large variety of potential risks

Incentivized

• SonarLint highlights all the issues in our codes and also displays the severity of each issue.
• SonarLint also provides suggestions for how to fix those code issues which are highlighted.
• SonarLint starts the processing of the file as soon as it is opened and highlights all the issues which it found.
• When we fix the issue, we don't even need to create a new build or generate fresh code quality report, as soon as we save the file with the changes, it does the processing again and shows the result if the issue is fixed or not.
• SonarLint saves a lot of time and effort by saving us from doing fresh build every time and generating new code quality report every time, thus increasing the efficiency and output which is in return beneficial for the client.

Incentivized

• DAST capability can be the one where it does not support native use case of using OTP based arch
• API Scanning is something that lacks a bit due to not much customizations
• Branch wise reports for SAST is not available

Incentivized

• Sometimes, SonarLint does not highlight the issues in the code correctly.
• The severity of the issues highlighted is according to the default rules set, we should also be given authority to set the severity of the issues.
• The default fixes which SonarLint provides should be more enhanced and there should be more fixes available.
• Sometimes it takes a lot of time for processing of the file when any new file is loaded or changes are saved in a file.

Incentivized

Checkmarx's usability is generally good, but it can be a bit complex for new users. The interface may take some time to get used to, especially for those unfamiliar with security tools. Once you become familiar with it, it’s effective and integrates well into development workflows.

Incentivized

Checkmarx is easier to integrate with development tools and gives quick feedback during coding, which is helpful for developers. Veracode is more focused on scanning and reporting for compliance, but it’s more complex to set up. We chose Checkmarx because it fits better into our development process, offering faster scans and more useful suggestions for fixing problems

Incentivized

SonarLint works along with SonarQube

Incentivized

• Great diversity of vulnerabilities covered.
• Quicker scans
• They are feature rich compared to other tools I used in the past.
• Dashboards are not customizable enough.
• High number of false positives take up time and sometimes make our report look bad.

Incentivized

• SonarLint helps in achieving all the business requirements in a more efficient way.
• It reduces the manual and redundant work which we would have to do else every time if we did not use SonarLint.
• SonarLint helps in maintaining code quality, and thus also highlights the loopholes for the cyber attacks and phishing attacks.
• SonarLint makes work easy and helps the developer to invest less time in manual work thereby increasing their capacity to deliver the maximum output to the client.

Incentivized