SonarQube for IDE (formerly SonarLint) Reviews

SonarQube for IDE (formerly SonarLint) is used for source code scanning to check for vulnerabilities, memory leaks, and any unnecessary code in the code.

Real-time analysis is utilized with SonarQube for IDE (formerly SonarLint).

After implementing SonarQube for IDE (formerly SonarLint), vulnerability reports are quickly generated as it integrates with the CI, providing effective daily scans to identify what needs to be fixed.

Historical data from SonarQube for IDE (formerly SonarLint) is used to track code quality evolution by comparing code fixes and reflecting on the reduction of vulnerabilities with each release.

SonarQube for IDE (formerly SonarLint) is easy to integrate with CI pipelines, which is a strong aspect of the product.

Real-time analysis definitely improves code quality because everyday scans produce reports and predict vulnerabilities that can turn into exploits.

Integration with SonarQube for IDE (formerly SonarLint) servers helps the team prioritize project actions effectively.

SonarQube for IDE (formerly SonarLint) helps identify the root cause early, which is beneficial in reducing technical debt.

SonarQube for IDE (formerly SonarLint) could improve by giving more details about the fixes for particular vulnerabilities and by plotting the dependency trees.

In future updates, it would be beneficial to see SonarQube for IDE (formerly SonarLint) able to scan AI models and analyze the vulnerability loopholes in AI, as AI is the next upcoming trend.

SonarQube for IDE (formerly SonarLint) has been used for almost five to six years.

SonarQube for IDE (formerly SonarLint)'s technical support is responsive and helpful.

The deployment for SonarQube for IDE (formerly SonarLint) was done by the central team, and our team runs our products on top of it.

The deployment was done by a different team.

I am not certain how many people were involved in the deployment because the deployment team, like the tool team itself, is different. They do the deployment for different tools, and as a security person, I just need to do a scan of our products with those tools.

The deployment required a quick timeframe of within a week.

We are using SonarQube for IDE (formerly SonarLint) for our SAST function.

SonarQube for IDE (formerly SonarLint) has come up with SCA and secret scanning capabilities, which are really good features for IDE.

From SonarQube for IDE (formerly SonarLint)'s perspective, one thing is that the SCA capability which they are coming up with gives vulnerabilities, hotspots, and code smells.

The dashboard could be simpler, and if I could see all the vulnerabilities of a specific project in one view, which is not possible as of today, that would be helpful.

Integration with third-party tools is another area where I think there is room for improvement as of now.

I have been using this solution for seven or eight years.

Support depends on the license. I would rate this a four because sometimes we do not get support on time when it is required, and other customers are blocked because of some changes or other issues. On the support side, I would recommend improvement.

Positive

In my previous organization, we also used SonarQube for IDE (formerly SonarLint) for the same task, so I have been working with it for three or four years.

When I joined the organization, SonarQube for IDE (formerly SonarLint) was already deployed, so I am not the right person to answer this question as it is a tool and technology that was already deployed. Deployment was done by one person, but that person had to coordinate and collaborate with different teams to onboard the projects. From a deployment perspective, one person handled it.

My overall rating for SonarQube for IDE (formerly SonarLint) is 7.5 out of 10.