GitHub Code Scanning vs Invicti comparison

Read 31 Invicti reviews

3,717 Views
2,379 Comparison Views

96% willing to recommend

GitHub Code Scanning

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Oct 8, 2024

Invicti and GitHub Code Scanning are competitors in the software security space. Based on features and user satisfaction, Invicti shows stronger customer support, while GitHub Code Scanning benefits from integration with developer workflows.

Features: Invicti offers comprehensive threat detection, flexible integration, and extensive security tools. GitHub Code Scanning provides robust integration with developer workflows, automation features, and seamless GitHub repository integration.

Room for Improvement: Invicti could improve scanning speed, report accuracy, and user interface. GitHub Code Scanning users desire better documentation, more intuitive configuration, and easier initial setup.

Ease of Deployment and Customer Service: Invicti offers straightforward deployment and exceptional customer service. GitHub Code Scanning is well-integrated for GitHub users but may be challenging for newcomers, impacting user experience.

Pricing and ROI: Invicti's pricing is seen as favorable, contributing to a good ROI. GitHub Code Scanning's higher pricing is justified by its feature set, making it a valuable option when feature requirements align with its offerings.

To learn more, read our detailed GitHub Code Scanning vs. Invicti Report (Updated: March 2026).

GitHub Code Scanning vs. Invicti

Download the complete report

Helped 884,797 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)

14th

Average Rating

8.6

Reviews Sentiment

6.7

Number of Reviews

Ranking in other categories

No ranking in other categories

Invicti

Ranking in Static Application Security Testing (SAST)

11th

Average Rating

8.2

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Container Security (25th), Software Composition Analysis (SCA) (8th), API Security (8th), Dynamic Application Security Testing (DAST) (4th), Application Security Posture Management (ASPM) (5th)

Mindshare comparison

As of March 2026, in the Static Application Security Testing (SAST) category, the mindshare of GitHub Code Scanning is 1.6%, up from 0.9% compared to the previous year. The mindshare of Invicti is 1.5%, up from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Static Application Security Testing (SAST) Mindshare Distribution
Product	Mindshare (%)
Invicti	1.5%
GitHub Code Scanning	1.6%
Other	96.9%

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

Valavan Sivgalingam

Senior Manager, Security Engineering at ESS

Dynamic testing regularly identifies web vulnerabilities and has strong false positive confirmations

It has good false positive confirmations, confirmed issues identification, and proof of exploit-related features as part of it. We use Invicti for these things in our portfolios. The solution includes Proof-Based Scanning technology. Invicti is part of our SSDLC portfolio, and DAST dynamic testing is very important for our web applications and portfolios. For both the API endpoints and web applications, we do regular testing on a monthly basis for all our releases. Invicti does a good job. The only concern is on the performance side, but other than that, we find it really helpful in identifying web vulnerabilities. A full scan takes more time based on your website and other factors, but for us, it takes more than two to three days. The scan performance can be improved upon. When we check with them, they discuss proof-based scanning and related aspects. However, there could be intermittent results that could help us.

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

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

"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 Scanning has positively impacted my organization as it helps us recognize errors and avoid many later issues which may arise."

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

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

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

"The platform is stable."

"This tool is really fast and the information that they provide on vulnerabilities is pretty good."

"I like that it's stable and technical support is great."

"Invicti's proactive scanning measures vulnerabilities each time we deploy or push code to a new environment."

"Its ability to crawl a web application is quite different than another similar scanner."

"The scanner is light on the network and does not impact the network when scans are running."

"It has very good integration with the CI/CD pipeline."

"Invicti is part of our SSDLC portfolio, and DAST dynamic testing is very important for our web applications and portfolios."

More Invicti pros

Cons

"GitHub Code Scanning should add more templates."

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

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

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

"Maybe the ability to make a good reporting format is needed."

"The scanner itself should be improved because it is a little bit slow."

"The solution's false positive analysis and vulnerability analysis libraries could be improved."

"The licensing model should be improved to be more cost-effective. There are URL restrictions that consume our license. Compared to other DAST solutions and task tools like WebInspect and Burp Enterprise, Invicti is very expensive. The solution’s scanning time is also very long compared to other DAST tools. It might be due to proof-based scanning."

"The support's response time could be faster since we are in different time zones."

"They don't really provide the proof of concept up to the level that we need in our organization. We are a consultancy firm, and we provide consultancy for the implementation and deployment solutions to our customers. When you run the scans and the scan is completed, it only shows the proof of exploit, which really doesn't work because the tool is running the scan and exploiting on the read-only form. You don't really know whether it is actually giving the proof of exploit. We cannot prove it manually to a customer that the exploit is genuine. It is really hard to perform it manually and prove it to the concerned development, remediation, and security teams. It is currently missing the static application security part of the application security, especially web application security. It would be really cool if they can integrate a SAS tool with their dynamic one."

"Invicti's reporting capabilities need enhancement."

"They need to improve their support in the documentation. Their support mechanism is missing. Their responsiveness, technical staff, and these types of things need to be improved, and comprehensive documentation is required. They should have good self-service portal enhancement"

More Invicti cons

Pricing and Cost Advice

"GitHub Code Scanning is a moderately priced solution."

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

"I think that price it too high, like other Security applications such as Acunetix, WebInspect, and so on."

"The solution is very expensive. It comes with a yearly subscription. We were paying 6000 dollars yearly for unlimited scans. We have three licenses; basic, business, and ultimate. We need ultimate because it has unlimited scan numbers."

"We never had any issues with the licensing; the price was within our assigned limits."

"Invicti is best suited for large enterprises. I don't think small and medium-sized businesses can afford it. Maintenance costs aren't that great."

"We are using an NFR license and I do not know the exact price of the NFR license. I think 20 FQDN for three years would cost around 35,000 US Dollars."

"The price should be 20% lower"

"OWASP Zap is free and it has live updates, so that's a big plus."

"Netsparker is one of the costliest products in the market. It would help if they could allow us to scan multiple URLs on the same license."

More Invicti pricing and cost advice

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

884,797 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Computer Software Company

11%

Manufacturing Company

Financial Services Firm

Government

Financial Services Firm

15%

Manufacturing Company

Computer Software Company

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

By reviewers
Company Size	Count
Small Business	14
Midsize Enterprise	4
Large Enterprise	13

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.

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

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

What is your experience regarding pricing and costs for Netsparker Web Application Security Scanner?

The setup cost is pretty competitive. For example, if you want to talk about the SAST license, it comes to about $150 or sometimes less than $100, depending on the conversion or the number of licen...

What needs improvement with Invicti?

At this time, there is nothing that comes to mind. However, most of the products in the market are pretty much neck-to-neck competitors. Speaking about it, there are a couple of factors which they ...

What is your primary use case for Invicti?

I have worked on a couple of products, specifically in web application security. I have worked on Invicti, and with respect to PAM, I have worked with BeyondTrust. I have not worked specifically fo...

SonarQube vs GitHub Code Scanning

Comparisons

Compared 22% of the time

Coverity Static vs GitHub Code Scanning

Compared 12% of the time

Aikido Security vs GitHub Code Scanning

Compared 7% of the time

HCL AppScan vs GitHub Code Scanning

Compared 6% of the time

Contrast Security Assess vs GitHub Code Scanning

Compared 2% of the time

More GitHub Code Scanning Competitors

Acunetix vs Invicti

Compared 9% of the time

Veracode vs Invicti

Compared 8% of the time

SonarQube vs Invicti

Compared 6% of the time

OpenText Dynamic Application Security Testing vs Invicti

Compared 5% of the time

Rapid7 InsightAppSec vs Invicti

Compared 4% of the time

More Invicti Competitors

Product Reports

GitHub Code Scanning

Download GitHub Code Scanning product report

Download Invicti product report

Also Known As

No data available

Netsparker

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

Invicti helps DevSecOps teams automate security tasks and save hundreds of hours each month by identifying web vulnerabilities that matter. Combining dynamic with interactive testing (DAST + IAST) and software composition analysis (SCA), Invicti scans every corner of an app to find what other tools miss with 99.98% accuracy, delivering on the promise of Zero Noise AppSec. Invicti helps discover all web assets — even ones that are lost, forgotten, or created by rogue departments. With an array of out-of-the-box integrations, DevSecOps teams can get ahead of their workloads to hit critical deadlines, improve processes, and communicate more effectively while reducing risk and hitting the ROI goals.

Sample Customers

Information Not Available

Samsung, The Walt Disney Company, T-Systems, ING Bank

GitHub Code Scanning vs. Invicti