GitHub Code Scanning vs Klocwork comparison

GitHub and Perforce are both solutions in the Static Application Security Testing (SAST) category. GitHub is ranked #12 with an average rating of 8.2, while Perforce is ranked #14 with an average rating of 7.8. GitHub holds a 1.4% mindshare in SAST, compared to Perforce’s 1.4% 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

2,016 Views
1,935 Comparison Views

100% willing to recommend

Klocwork

Read 25 Klocwork reviews

4,617 Views
2,678 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: April 2026).

Buyer's Guide

GitHub Code Scanning vs. Klocwork

April 2026

Download the complete report

Helped 893,164 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)

12th

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)

14th

Average Rating

8.0

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Application Security Tools (18th), Static Code Analysis (3rd)

Mindshare comparison

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

Static Application Security Testing (SAST) Mindshare Distribution
Product	Mindshare (%)
GitHub Code Scanning	1.4%
Klocwork	1.4%
Other	97.2%

Static Application Security Testing (SAST)

Featured Reviews

AbhishekKumar20

Software Development Manager at Amazon

Code scanning identifies vulnerabilities quickly and improves team response with minimal setup

I have been using Git for approximately 13-14 years. I have used GitHub Code Scanning for about three to four years. The primary purpose is to identify any vulnerability in the code itself. The system logs vulnerabilities that we can immediately examine to see all the error-prone areas. The AI functionalities include predefined agents that scan through and immediately provide responses regarding the best nomenclature or code coverage percentage. It's actually a one-time setup, and the team benefits as long as they push code and changes in the repository itself. Every time we push something, we immediately check the total deviation, whether our code coverage has improved, or if any vulnerability has been identified. There is always a metrics dashboard that we can see and identify. Primarily, GitHub is used for doing the versioning itself in the repository. With vulnerability functionality being provided and AI agents available, it makes a complete package. As soon as we publish our code, we immediately get to know the test code coverage. This immediately informs us about all the vulnerable areas which are not being fully tested. If we address those areas, most vulnerabilities are resolved. Even after tests are added, if by any chance the test is not treated cleanly or corner cases are missed, GitHub Code Scanning immediately flags those corners. It's always beneficial to have because it's not humanly possible to check all corner case scenarios, but as a system where they diagnose each line item, that's very helpful.

Read full review

Krishna M Gopalakrishnan

Manager, Quality, Functional Safety, Cybersecurity Embedded Processing at a manufacturing company with 10,001+ employees

Experience with compliance improvements and efficiency boosts but static analysis engine shows a need for enhancement

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 improvement. Customers using different static analysis tools report more issues than with Klocwork, indicating that Klocwork's engine is not as superior. Klocwork should be able to analyze large codebases efficiently, supporting a desktop version for periodic small delta changes before pushing to the server.

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

"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."

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

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

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

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

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

"On-the-fly analysis and incremental analysis are the best parts of Klocwork, and currently we are using both of these features very effectively."

"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."

"Klocwork is a good product, but keep in mind that before building the code you have to get a report."

"The ability to create custom checkers is a plus."

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

"It saves a lot of time when it comes to finding defects, it's basically inputted in every access we do."

"We like using the static analysis and code refactoring, which are very valuable because of our requirements to meet safety critical levels and reliability."

"Klocwork's most valuable feature is the static code analysis feature. It detects the potential problem earlier to allow the developer to receive feedback quickly and then address it before it becomes a problem."

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."

"GitHub Code Scanning should add more templates."

"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."

"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."

"Klocwork sometimes provides too many additional warnings which require expertise to manage."

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

"This solution could be improved if they offered support of more languages including Ada and Golang. They currently only support seven languages."

"For an improved product, we'd like to see integration with Agile DevOps and Agile methodologies."

"The main problem is that since it only parses the code, the warnings or the problems that are given as a result of the report can sometimes require a lot of effort to analyze."

"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."

"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."

"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."

More Klocwork cons

Pricing and Cost Advice

"GitHub Code Scanning is a moderately priced solution."

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

"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."

"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."

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

"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."

"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."

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

"This solution offers competitive pricing."

"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."

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

893,164 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Computer Software Company

11%

Financial Services Firm

10%

Manufacturing Company

10%

Retailer

Manufacturing Company

22%

Computer Software Company

Transportation Company

Construction Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

By reviewers
Company Size	Count
Small Business	12
Midsize Enterprise	2
Large Enterprise	12

Questions from the Community

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 advice do you have for others considering GitHub Code Scanning?

I am an end user only here with GitHub Code Scanning. I currently might be using the latest version of GitHub Code Scanning, but I don't remember the specific version. I have not utilized the real-...

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?

See all answers

What is your primary use case for Klocwork?

I work on tools such as Klocwork, LDRA, as well as Jira and Confluence, focusing more on the software quality assurance aspect. We use Klocwork for coding and aggregate checks. We use it for static...

See all answers

Comparisons

SonarQube vs GitHub Code Scanning

Compared 16% of the time

Coverity Static vs GitHub Code Scanning

Compared 10% of the time

Aikido Security vs GitHub Code Scanning

Compared 6% of the time

HCL AppScan vs GitHub Code Scanning

Compared 6% of the time

Veracode vs GitHub Code Scanning

Compared 5% of the time

More GitHub Code Scanning Competitors

SonarQube vs Klocwork

Compared 13% of the time

Coverity Static vs Klocwork

Compared 11% of the time

Polyspace Code Prover vs Klocwork

Compared 7% of the time

Helix QAC vs Klocwork

Compared 6% of the time

Checkmarx One vs Klocwork

Compared 4% of the time

More Klocwork Competitors

Product Reports

Buyer's Guide

GitHub Code Scanning

April 2026

Download GitHub Code Scanning product report

Buyer's Guide

Klocwork

April 2026

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 offers advanced static code analysis with integration capabilities for enhanced development efficiency, supporting various development environments and providing clear defect reports. It streamlines software development by reducing defects and improving code quality.

Klocwork integrates seamlessly into CI/CD pipelines, providing real-time and incremental analysis to identify and rectify code defects quickly. It supports multiple integrated development environments (IDEs) and minimizes false positives in its analysis. While primarily supporting C/C++, Java, and C#, there is a need to expand language support and enhance its static analysis engine. The tool assists in adhering to industry standards with features like automated code parsing and MISRA compliance checks. Ease of setup and collaboration capabilities further promotes efficiency, although the dashboard could benefit from user-friendly updates and better integration with Agile tools.

What are the primary features of Klocwork?

Static Code Analysis: Identifies vulnerabilities and defects in code with reduced false positives.
CI/CD Integration: Seamlessly embeds into continuous integration and delivery pipelines for efficient testing.
Customizable Checkers: Allows users to tailor checkers according to specific project needs.
On-the-fly Analysis: Provides incremental analysis to detect issues during coding, reducing development time.
IDE Support: Functions across multiple IDEs, enhancing developer workflow and productivity.

What benefits should users expect from Klocwork?

Reduced Development Time: By detecting issues early, faster development cycles are achieved.
Improved Code Quality: Helps in maintaining high code standards and adherence to compliance checks.
Efficient Collaboration: Streamlines team collaboration with easy integration and analysis reports.
Enhanced Maintainability: Through automation and efficient detection of memory-related and security issues.

Klocwork is extensively implemented in industries that prioritize software quality and security standards, particularly in environments focused on C/C++ development on Linux systems. Its capabilities in automated code parsing, traffic analysis, and support for DevOps integration make it invaluable for industries requiring strict MISRA compliance and internal standards adherence. By aiding refactoring and detecting memory-related vulnerabilities, Klocwork contributes to the maintainability and security standards in these sectors.

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

April 2026

Free Report: GitHub Code Scanning vs. Klocwork

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

DOWNLOAD NOW

893,164 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.