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
35th
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
12th
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
36
Ranking in other categories
Non-Human Identity Management (NHIM) (5th)
 

Mindshare comparison

As of August 2026, in the Application Security Tools category, the mindshare of CodeSonar is 1.0%, down from 1.5% compared to the previous year. The mindshare of GitGuardian Platform is 1.7%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools Mindshare Distribution
ProductMindshare (%)
GitGuardian Platform1.7%
CodeSonar1.0%
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

"It has helped us a lot with some issues and has helped us avoid bad code."
"The tool is very good for detecting memory leaks."
"The solution is very stable and we have used it for a long time with no issues."
"The most valuable features of CodeSonar were all the categorized classes provided, and reports of future bugs which might occur in the production code. Additionally, I found the buffer overflow and underflow useful."
"It has been able to scale."
"There is nice functionality for code surfing and browsing."
"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."
"The stability of the GitGuardian Platform is excellent."
"GitGuardian public leak detection significantly enhances our organization's data security by continuously monitoring public repositories."
"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."
"It enables us to identify leaks that happened in the past and remediate current leaks as they happen in near real-time. When I say "near real-time," I mean within minutes. These are industry-leading remediation timelines for credential leaks. Previously, it might have taken companies years to get credentials detected or remediated. We can do it in minutes."
"You can also assign tasks to specific teams or people to complete, such as assigning something to the "blue team" or saying that this person needs to do this, and that person needs to do that. That is a great feature because you can actually manage your team internally in GitGuardian."
"What is particularly helpful is that having GitGuardian show that the code failed a check enables us to automatically pass the resolution to the author. We don't have to rely on the reviewer to assign it back to him or her. Letting the authors solve their own problems before they get to the reviewer has significantly improved visibility and reduced the remediation time from multiple days to minutes or hours. Given how time-consuming code reviews can be, it saves some of our more scarce resources."
"Time to remediation is now in minutes or hours, whereas it used to take days or weeks previously."
"GitGuardian has increased our detection rate by a factor of 10 at least."
 

Cons

"It was expensive."
"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."
"CodeSonar could improve by having better coding rules so we did not have to use another solution, such as MISRA C."
"The scanning tool for core architecture could be improved."
"The MISRA guidelines were not appropriately reported and there were some flags or errors."
"It would be beneficial for the solution to include code standards and additional functionality for security."
"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."
"GitGuardian encompasses many secrets that companies might have, but we are a Microsoft-only organization, so there are some limitations there in terms of their honey tokens. I'd like for it to not be limited to Amazon-based tokens. It would be nice to see a broader set of providers that you could pick from."
"The main disadvantage I feel they should improve upon is that apart from flagging credential issues or secrets, they could incorporate something else to make it more dynamic."
"It would be nice if they supported detecting PII or had some kind of data loss prevention feature."
"Right now, we are waiting for improvement in the RBAC support for GitGuardian."
"One improvement that I'd like to see is a cleaner for Splunk logs. It would be nice to have a middle man for anything we send or receive from Splunk forwarders. I'd love to see it get cleaned by GitGuardian or caught to make sure we don't have any secrets getting committed to Splunk logs."
"GitGuardian Platform has the occasional false positive in testing."
"GitGuardian could have more detailed information on what software engineers can do. It only provides some highly generic feedback when a secret is detected. They should have outside documentation. We send this to our software engineers, who are still doing the commits. It's the wrong way to work, but they are accustomed to doing it this way. When they go into that ticket, they see a few instructions that might be confusing. If I see a leaked secret committed two years ago, it's not enough to undo that commit. I need to go in there, change all my code to utilize GitHub secrets, and go on AWS to validate my key."
"I would like to see improvement in some of the user interface features."
 

Pricing and Cost Advice

"Our organization purchased a license to use the solution."
"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."
"Pricing is a bit costly."
"With GitGuardian, we didn't need any middlemen."
"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."
"We don't have a huge number of users, but its yearly rate was quite reasonable when compared to other per-seat solutions that we looked at... Having a free plan for a small number of users was really great. If you're a small team, I don't see why you wouldn't want to get started with it."
"It's a bit expensive, but it works well. You get what you pay for."
"It's a little bit expensive."
"GitGuardian is on the pricier side."
"It's competitively priced compared to others. Overall, the secret detection sector is expensive, but we are very happy with the value we get."
"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."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
23%
Computer Software Company
8%
University
7%
Financial Services Firm
7%
Outsourcing Company
16%
Comms Service Provider
12%
Construction Company
10%
Financial Services Firm
8%
 

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 Business21
Midsize Enterprise9
Large Enterprise24
 

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: August 2026.
909,725 professionals have used our research since 2012.