GitHub Code Scanning vs Klocwork comparison

GitHub and Perforce are both solutions in the Static Application Security Testing (SAST) category. GitHub is ranked #17 with an average rating of 8.5, while Perforce is ranked #16 with an average rating of 8.1. GitHub holds a 1.3% mindshare in SAST, compared to Perforce’s 1.6% mindshare. Additionally, 100% of GitHub users are willing to recommend the solution, compared to 93% of Perforce users who would recommend it.

GitHub Code Scanning

Read 6 GitHub Code Scanning reviews

1,016 Views
965 Comparison Views

100% willing to recommend

Klocwork

Read 25 Klocwork reviews

3,592 Views
2,730 Comparison Views

93% willing to recommend

GitHub Code Scanning

Klocwork

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Oct 8, 2024

Klocwork and GitHub Code Scanning are prominent tools in the static code analysis category. GitHub Code Scanning has an upper hand due to its seamless integration and functionality within existing development workflows.

Features: Klocwork offers robust detection of security vulnerabilities and code issues, extensive customization options, and comprehensive support. GitHub Code Scanning integrates smoothly into development workflows, supports multiple programming languages, and enhances productivity in CI/CD pipelines.

Room for Improvement: Klocwork needs enhancements in documentation, user training resources, and simplifying its initial setup process. GitHub Code Scanning is advised to improve accuracy, reduce false positives, and provide more detailed analysis reports. Improving direct customer support could be beneficial.

Ease of Deployment and Customer Service: Klocwork's initial setup is complex but is offset by its responsive customer support. GitHub Code Scanning offers simple deployment within GitHub's ecosystem, relying more on community forums for support.

Pricing and ROI: Klocwork stands out for its reasonable setup costs and positive ROI due to robust features. GitHub Code Scanning, although having higher initial pricing, delivers ROI through workflow efficiencies and feature richness.

To learn more, read our detailed GitHub Code Scanning vs. Klocwork Report (Updated: July 2025).

Buyer's Guide

GitHub Code Scanning vs. Klocwork

July 2025

Download the complete report

Helped 865,384 peers since 2012

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

GitHub Code Scanning

Ranking in Static Application Security Testing (SAST)

17th

Average Rating

8.6

Reviews Sentiment

6.7

Number of Reviews

Ranking in other categories

No ranking in other categories

Klocwork

Ranking in Static Application Security Testing (SAST)

16th

Average Rating

8.0

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Application Security Tools (18th), Static Code Analysis (5th)

Mindshare comparison

As of August 2025, in the Static Application Security Testing (SAST) category, the mindshare of GitHub Code Scanning is 1.3%, up from 0.3% compared to the previous year. The mindshare of Klocwork is 1.6%, down from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Static Application Security Testing (SAST)

Featured Reviews

VishalSingh

Consulting & Solutions, BA/BD in Enterprise IT on Open Source, Red Hat & EDB at KEEN AND ABLE COMPUTERS PVT LTD

Traverses the entire network, scanning every system to determine which ports are open

You can use the tool locally on your system or in the cloud. I rate it a nine out of ten. It's a very good tool for people who want to start using GitHubCode Scanning, especially for software development or team collaboration. GitHubCode Scanning allows teams to collaborate by uploading files to repositories. For example, if someone is developing an application, they can host the code on GitHub Code Scanning. Other developers can then download the code for testing purposes. If bugs are found, fixes can be applied using the GitHub Code Scanningrepository, and everyone on the team can see the changes. Software developers often use GitHub Code Scanning for version control, and it's essential for CI/CD pipelines to work.

Read full review

AnirbanSarkar

Head - Solution Management Group at Meteonic Innovation Pvt. Ltd.

Lets you find defects during the development phase, so you don't have to wait till the development is over to find and address flaws

What needs improvement in Klocwork, compared to other products in the market, is the dashboard or reporting mechanisms that need to be a bit more flexible. The Klocwork dashboard could be improved. Though it's good, it's not as good as some of the other products in the market, which is a problem. The reporting could be more detailed and easier to sort out because sorting in Klocwork could be a bit more time-consuming, mainly when sorting defects based on filters, compared to how it's done on other tools such as Coverity. What I'd like added in the next release of Klocwork is the peer code review Cahoots which used to be a part of Klocwork, and the architecture analysis and both have been taken out of Klocwork. I found the two critical for specific deployments, so if those can be brought back to Klocwork, that would be very good.

Read full review

Quotes from Members

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

Pros

"GitHub Code Spaces brings significant value with its simplicity and ease of use."

"We use GitHub Code Scanning mostly for source code management."

"GitHub Code Scanning has positively impacted my organization as it helps us recognize errors and avoid many later issues which may arise."

"The static code analysis capability in GitHub Code Scanning is a very powerful feature, providing the ability to identify vulnerabilities and ensure code quality."

"The solution helps identify vulnerabilities by understanding how ports communicate with applications running on a system. Ports are like house numbers; to visit someone's house, you must know their number. Similarly, ports are used to communicate with applications. For example, if you want to use an HTTP web server, you must use port 80. It is the port on which the web application or your server listens for incoming requests."

"It's very scalable, very easy to handle, and very intuitive."

"The best advantage of Klocwork is the reduced setup time."

"There is a central Klocwork server at our headquarter in France so we connect the client directly to the server on-premises remotely."

"The reporting helps us understand the trend of our results and whether we improve over time. We can see the history within Klocwork's server architecture and know that we're making things better. It creates a great story for our management. We can demonstrate value and how our software is developing over time."

"It's integrated into our CI, continuous integration."

"The customer support team is very responsive, proactive, and engages in conversations to ensure our needs are met."

"Klocwork is user-friendly, with a client-server architecture that provides all needed compliance."

"The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time."

"The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies. I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python."

More Klocwork pros

Cons

"One area for improvement could be the ability to have an AI system digest the reports generated from code scanning and provide a summary. Currently, the reports can be extensive, and users may overlook details, such as outdated libraries, which could be highlighted for attention."

"At times it becomes very annoying as it highlights certain things which are intuitive. They require code coverage for those aspects as an extra overhead."

"When running code scans, GitHub Code Scanning provides recommendations for probable fixes. However, integrating a feature where developers receive real-time highlights of vulnerabilities when checking in or merging a PR would be beneficial."

"GitHub Code Scanning should add more templates."

"Under NIST cybersecurity standards, we must address vulnerabilities within a specified time after discovering them. When we try to propagate those updates and fixes through the system, it would be nice if the clients could reconnect to the existing server or have the server dynamically updated in some way. I know that isn't easy, but maybe processes could be enhanced to make that more streamlined from a DevOps perspective."

"There are too many warnings, and it requires expertise to determine the correct category for them."

"Klocwork has to improve its features to stay ahead of other free solutions."

"I believe it should support more languages, such as Python and JavaScript."

"Every update that we receive requires of us a lengthy and involved process."

"We bought Klocwork, but it was limited to one little program, but the program is now sort of failing. So, we have a license for usage on a program that is sort of failing, and we really can't use the license on anything else."

"Now the only issue we have is that whenever we need to get the code we have to build it first. Then we can get the report."

"Klocwork does have a problem with true positives. It only found 30% of true positives in the Juliet test case."

More Klocwork cons

Pricing and Cost Advice

"The minimum pricing for the tool is five dollars a month."

"GitHub Code Scanning is a moderately priced solution."

"There are other solutions on the market such as Microsoft Visual Studio. They have been adding more static code analysis features that come for free. It is getting better all the time. That is one of the possibilities is that we've been considering that we may stop using the Klocwork because it doesn't give us any added value."

"Licensing fees are paid annually, but they also have a perpetual license."

"The pricing for Klocwork is very competitive if you compare it from apple to apple. It has competitive pricing regarding the licensing model and the per-license cost. Klocwork isn't a high-end investment for anyone deploying it; even SMBs can afford it. The Klocwork cost per user would depend on the license type, so I'm unable to mention a ballpark figure because it would depend on the type of installation and how the deployment will be, and the nodes to give an accurate calculation or figure. The total price depends on the package, so my company could never publish pricing for Klocwork on the website. My team first collects information from potential clients on the deployment scenario, project environment, etc., before suggesting a package for Klocwork. My rating for Klocwork in terms of pricing is a five because of its flexible license models. There's a license model for every type of organization, whether small, midsize, or enterprise, so it's a five out of five for me."

"Klocwork should not to be quite so heavy handed on the licensing for very specific programs."

"This solution offers competitive pricing."

"The limitation that we have is that Klocwork is licensed to certain programs, and if you want to license them to other programs, you have to pay more money."

"When it comes to licensing, the solution has two packages, one for a fixed and the other for a floating server, with the former being more cost effective than the latter."

"Klocwork is still tight on their licensing. If Klocwork would loosen up on the licensing, and where the license could be used, and how many different programs could be run on it, then we have several development programs that I would love to be able to use it for going forward."

See which vendors are best for you

Use our free recommendation engine to learn which Static Application Security Testing (SAST) solutions are best for your needs.

See recommendations

865,384 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Computer Software Company

13%

Financial Services Firm

11%

Manufacturing Company

10%

Government

Manufacturing Company

26%

Computer Software Company

13%

Comms Service Provider

Aerospace/Defense Firm

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about GitHub Code Scanning?

We use GitHub Code Scanning mostly for source code management.

See all answers

What is your experience regarding pricing and costs for GitHub Code Scanning?

The organization pays for the license of GitHub Code Scanning, but specific price details are unknown.

See all answers

What needs improvement with GitHub Code Scanning?

In my opinion, areas of GitHub Code Scanning that could be improved include that a few things are not visible to us, such as where it stores data and which path. There is a separate team for that w...

See all answers

What do you like most about Klocwork?

It's integrated into our CI, continuous integration.

See all answers

What is your experience regarding pricing and costs for Klocwork?

Klocwork's pricing seems attractive, as it uses a per-user license model that does not have a lot of overhead.

See all answers

What needs improvement with Klocwork?

One area for improvement is that when customers use different static analysis tools, they report more issues compared to Klocwork. The static analysis engine of Klocwork has areas that need improve...

See all answers

Comparisons

SonarQube Server (formerly SonarQube) vs GitHub Code Scanning

Compared 33% of the time

Coverity vs GitHub Code Scanning

Compared 24% of the time

SonarQube Cloud (formerly SonarCloud) vs GitHub Code Scanning

Compared 11% of the time

Aikido Security vs GitHub Code Scanning

Compared 9% of the time

HCL AppScan vs GitHub Code Scanning

Compared 7% of the time

More GitHub Code Scanning Competitors

SonarQube Server (formerly SonarQube) vs Klocwork

Compared 29% of the time

Coverity vs Klocwork

Compared 28% of the time

Polyspace Code Prover vs Klocwork

Compared 13% of the time

Helix QAC vs Klocwork

Compared 6% of the time

Axivion Static Code Analysis vs Klocwork

Compared 5% of the time

More Klocwork Competitors

Product Reports

Buyer's Guide

GitHub Code Scanning

August 2025

Download GitHub Code Scanning product report

Buyer's Guide

Klocwork

August 2025

Download Klocwork product report

Overview

Code scanning is a feature that you use to analyze the code in a GitHub repository to find security vulnerabilities and coding errors. Any problems identified by the analysis are shown in GitHub.

GitHub

Klocwork detects security, safety, and reliability issues in real-time by using this static code analysis toolkit that works alongside developers, finding issues as early as possible, and integrates with teams, supporting continuous integration and actionable reporting.

Perforce

Sample Customers

Information Not Available

ACCESS Co Ltd, Risk-AI, Winbond Electronics, Bristol-Myers Squibb Pharmaceutical Research Institute, University of Southern California, Alebra Technologies, SIMULIA, Risk Management Solutions, Brigham Young University, SRD, HRL

Buyer's Guide

GitHub Code Scanning vs. Klocwork

July 2025

Free Report: GitHub Code Scanning vs. Klocwork

Find out what your peers are saying about GitHub Code Scanning vs. Klocwork and other solutions. Updated: July 2025.

DOWNLOAD NOW

865,384 professionals have used our research since 2012.

See our GitHub Code Scanning vs. Klocwork report.

See our list of best Static Application Security Testing (SAST) vendors.

We monitor all Static Application Security Testing (SAST) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.