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

Mindshare comparison

As of May 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 App
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

"The most valuable feature of CodeSonar is the catching of dead code. It is helpful."
"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."
"CodeSonar has helped our organization because it detects dead and nonusable parts of code to create a more optimized code."
"CodeSonar’s most valuable feature is finding security threats."
"The most valuable features of CodeSonar were all the categorized classes provided, and reports of future bugs which might occur in the production code."
"It has been able to scale."
"I would suggest trying out automated tools along with CodeSonar on your project, and you will find out that CodeSonar reports many more defects compared to other static analysis tools, so this is a very important tool."
"There is nice functionality for code surfing and browsing."
"GitGuardian Platform has helped save significant time for the security team by eliminating the need to seek out development teams and work with them on exposed secrets, as much of this is now handled proactively."
"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."
"Our company has remained very safe in this regard because we need to secure our data effectively, being in the insurance reinsurance sector."
"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, and I feel the solution bridged the gap between our team and the developers, which is really great."
"It's fantastic. We have checked a couple of other vendors and seen their results, which are quite inferior to the amount of detail that the GitGuardian Platform provides. With instantaneous notifications connected to our Slack platform, it allows us to deal quickly with incidents."
"GitGuardian has pretty broad detection capabilities. It covers all of the types of secrets that we've been interested in... [Yet] The "detector" concept, which identifies particular categories or types of secrets, allows an organization to tweak and tailor the configuration for things that are specific to its environment. This is highly useful if you're particularly worried about a certain type of secret and it can help focus attention, as part of early remediation efforts."
"Before we had GitGuardian we were blind; we had a lot of false positives with other products, but now GitGuardian has fewer false positives, its secrets detection is more accurate, and it has decreased our false positives by a minimum of 20 percent."
"GitGuardian has increased our detection rate by a factor of 10 at least."
 

Cons

"It would be beneficial for the solution to include code standards and additional functionality for security."
"CodeSonar could improve by having better coding rules so we did not have to use another solution, such as MISRA C."
"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."
"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."
"It was expensive."
"It would be beneficial for the solution to include code standards and additional functionality for security."
"It would be nice if they supported detecting PII or had some kind of data loss prevention feature."
"The main thing for me is the customization for some of the healthcare-specific identifiers that we want to validate. There should be some ability, which is coming in the near future, to have custom identifiers. Being in healthcare, we have pretty specific patterns that we need to match for PHI or PII. Having that would add a little bit extra to it."
"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."
"There is room for improvement in GitGuardian on Azure DevOps; the implementation is a bit hard there."
"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."
"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."
"One of our current challenges is that the GitGuardian platform identifies encrypted secrets and statements as sensitive information even though they're secured."
"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."
 

Pricing and Cost Advice

"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."
"Our organization purchased a license to use the solution."
"Pricing is a bit costly."
"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."
"The pricing and licensing are fair. It isn't very expensive and it's good value."
"The internal side is cheap per user. It is annual pricing based on the number of users."
"GitGuardian is on the pricier side."
"The pricing for GitGuardian is fair."
"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."
"It's a little bit expensive."
"It's a bit expensive, but it works well. You get what you pay for."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
893,438 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
8%
University
7%
Financial Services Firm
7%
Comms Service Provider
13%
Government
12%
Outsourcing Company
9%
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 Enterprise18
 

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: April 2026.
893,438 professionals have used our research since 2012.