No more typing reviews! Try our Samantha, our new voice AI agent.

CodeSonar vs GitGuardian Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 8, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CodeSonar
Ranking in Application Security Tools
30th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Static Code Analysis (10th)
GitGuardian Platform
Ranking in Application Security Tools
13th
Average Rating
8.8
Reviews Sentiment
7.1
Number of Reviews
34
Ranking in other categories
Non-Human Identity Management (NHIM) (8th)
 

Mindshare comparison

As of June 2026, in the Application Security Tools category, the mindshare of CodeSonar is 1.1%, down from 1.5% compared to the previous year. The mindshare of GitGuardian Platform is 1.6%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools Mindshare Distribution
ProductMindshare (%)
GitGuardian Platform1.6%
CodeSonar1.1%
Other97.3%
Application Security Tools
 

Featured Reviews

Mathieu ALBRESPY - PeerSpot reviewer
Intigration Developer at ez-Wheel
Nice interface, quick to deploy, and easy to expand
This is the first time I've used this kind of software. It was the only one we could apply to analyze with MISRA rules. At my new company, I tried to use Klocwork. I tried to use it, just once so I cannot compare it exactly with CodeSonar. I also have a plugin for my Visual Studio and I try to make it work. It's not easy, however, I don't think that we have this kind of functionality with CodeSonar. It can do some incremental analysis. However, since this feature is also available on CodeSonar, it would be a good idea to have a plugin on Visual Studio just to have a quick analysis.
Ney Roman - PeerSpot reviewer
DevOps Engineer at Deuna
Facilitates efficient secret management and improves development processes
Regarding the exceptions in GitGuardian Platform, we know that within the platform we have a way to accept a path or a directory from a repository, but it is not that visible at the very beginning. You have to figure out where to search for it, and once you have it, it is really good, but it is not that visible at the beginning. This should be made more exposed. The documentation could be better because it was not that comprehensively documented. When we started working with GitGuardian Platform, it was difficult to find some specific use cases, and we were not aware of that. It might have improved now, but at that time, it was not something we would recommend.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"There is nice functionality for code surfing and browsing."
"The tool is very good for detecting memory leaks."
"CodeSonar has helped our organization because it detects dead and nonusable parts of code to create a more optimized code."
"The most valuable feature of CodeSonar is the catching of dead code. It is helpful."
"It has helped us a lot with some issues and has helped us avoid bad code."
"It has been able to scale."
"CodeSonar’s most valuable feature is finding security threats."
"The solution is very stable and we have used it for a long time with no issues."
"GitGuardian Platform has positively impacted our organization by creating a strong security backbone and improving process efficiency, with one of the biggest outcomes being a significant reduction in sensitive data exposure incidents, as most credentials and tokens are caught at the commit or PR stage, leading to approximately thirty to forty percent reduction in security-related bugs over a few release cycles, which ultimately reduced manual effort."
"What I appreciate the most about GitGuardian Platform is its efficiency when triggering our pipeline and notifying us if secrets have been exposed, such as APIs, variables, our database, or anything being exposed."
"The most valuable feature is the general incident reporting system."
"The most valuable feature of GitGuardian is that it finds tokens and passwords. That's why we need this tool. It minimizes the possibility of security violations that we cannot find on our own."
"GitGuardian has helped to increase our security team's productivity. Now, we don't need to call the developers all the time and ask what they are working on. I feel the solution bridged the gap between our team and the developers, which is really great. I feel that we need that in our company, since some of the departments are just doing whatever and you don't know what they are doing. I think GitGuardian does a good job of bridging the gap. It saves us about 10 hours per week."
"The Explore function is valuable for finding specific things I'm looking for."
"The majority of our incidents for critical detectors and important secret types are remediated automatically or proactively by developers through GitGuardian's notification system, without security team involvement."
"The newest addition that we appreciate about GitGuardian Platform is the ability to create a custom detector, which we built and worked with the team, and that works very effectively."
 

Cons

"It would be beneficial for the solution to include code standards and additional functionality for security."
"The scanning tool for core architecture could be improved."
"In terms of areas for improvement, the use case for CodeSonar was good, but compared to other tools, it seems CodeSonar isn't a sound static analysis tool, and this is a major con I've seen from it. Right now, in the market, people prefer sound static analysis tools, so I would have preferred if CodeSonar was developed into a sound static analysis tool formally, in terms of its algorithms, so then you can see it extensively used in the market because at the moment, here in India, only fifty to sixty customers use CodeSonar. If the product is developed into a sound static analysis tool, it could compete with Polyspace, and from its current fifty customers, that number could go up to a hundred."
"There could be a shared licensing model for the users."
"It was difficult for us to apply a rule, especially to a part of the code, and not apply it to the rest of the code."
"It was expensive."
"CodeSonar could improve by having better coding rules so we did not have to use another solution, such as MISRA C."
"In a future release, the solution should upgrade itself to the current trends and differentiate between the languages. If there are any classifications that can be set for these programming languages that would be helpful rather than having everything in the generic category."
"I would like to see improvement in some of the user interface features."
"The analytics in GitGuardian Platform have a significant opportunity to better reflect the value provided to security teams and demonstrate actual activity occurring. While the self-healing capability and proactive developer actions are important features, the analytics do not provide information around this activity."
"There has been a little bit of downtime of late, and it has been reasonably impactful when it's not been scanning."
"The purchasing process is convoluted compared to Snyk, the other tool we use. It's like night and day because you only need to punch in your credit card, and you're set. With GitGuardian, getting a quote took two or three weeks. We paid for it in December but have not settled that payment yet."
"Although detection coverage is strong, there were initial cases where non-sensitive patterns were flagged, requiring tuning and allow-listing, which can be noisy at times."
"One of our current challenges is that the GitGuardian platform identifies encrypted secrets and statements as sensitive information even though they're secured."
"It would be nice if they supported detecting PII or had some kind of data loss prevention feature."
"I would like to see more fine-grained access controls when tickets are assigned for incidents. I would like the ability to provide more controls to the team leads or the product managers so that they can drive what we, the AppSec team, are doing."
 

Pricing and Cost Advice

"Our organization purchased a license to use the solution."
"Pricing is a bit costly."
"The solution's price depends on the number of licenses needed and the source code for the project."
"The application’s pricing is high compared to other tools."
"We have seen a return on investment. The amount of time that we would have spent manually doing this definitely outpaces the cost of GitGuardian. It is saving us about $35,000 a year, so I would say the ROI is about $20,000 a year."
"It could be cheaper. When GitHub secrets monitoring solution goes to general access and general availability, GitGuardian might be in a little bit of trouble from the competition, and maybe then they might lower their prices. The GitGuardian solution is great. I'm just concerned that they're not GitHub."
"I am only aware of the base price. I do not know what happened with our purchasing team in discussions with GitGuardian. I was not privy to the overall contract, but in terms of the base MSRP price, I found it reasonable."
"With GitGuardian, we didn't need any middlemen."
"You get what you pay for. It's one of the more expensive solutions, but it is very good, and the low false positive rate is a really appealing factor."
"The pricing for GitGuardian is fair."
"It's a bit expensive, but it works well. You get what you pay for."
"It's competitively priced compared to others. Overall, the secret detection sector is expensive, but we are very happy with the value we get."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
8%
Financial Services Firm
7%
University
7%
Comms Service Provider
13%
Outsourcing Company
10%
Government
10%
Financial Services Firm
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise2
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise9
Large Enterprise20
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for GitGuardian Internal Monitoring ?
It's competitively priced compared to others. Overall, the secret detection sector is expensive, but we are happy with the value we get.
What needs improvement with GitGuardian Internal Monitoring ?
GitGuardian Platform does what it is designed to do, but it still generates many false positives. We utilize the automated playbooks from GitGuardian Platform, and we are enhancing them. We will pr...
What is your primary use case for GitGuardian Internal Monitoring ?
Our current use cases for GitGuardian Platform involve monitoring external and internal GitHub and GitLab, Bitbucket, and other code repositories that it supports for secrets.
 

Also Known As

No data available
GitGuardian Internal Monitoring, GitGuardian Public Monitoring
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Viveris, Micrel Medical Devices, Olympus, SOFTEQ, SONY
Widely adopted by developer communities, GitGuardian is used by over 600 thousand developers and leading companies, including Snowflake, Orange, Iress, Mirantis, Maven Wave, ING, BASF, and Bouygues Telecom.
Find out what your peers are saying about CodeSonar vs. GitGuardian Platform and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.