GitHub Code Scanning vs Veracode comparison

Cancel
You must select at least 2 products to compare!
GitHub Logo
190 views|160 comparisons
100% willing to recommend
Veracode Logo
25,312 views|17,044 comparisons
90% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between GitHub Code Scanning and Veracode based on real PeerSpot user reviews.

Find out in this report how the two Static Application Security Testing (SAST) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed GitHub Code Scanning vs. Veracode Report (Updated: June 2024).
772,649 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"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."

More GitHub Code Scanning Pros →

"The most valuable feature of Veracode is the binary scan feature for auditing, which allows us to audit the software without the source code.""Static analysis scanning engine is a key feature.""The static analysis gives you deep insights into problems.""Veracode has good support for microservices, and I also like the sandbox environment. For example, when introducing a new component, we can scan it in a sandbox environment. It will not impact the main environment. When our team fixes it, they. can push it to the production environment when the results are acceptable.""Veracode supports a broad range of code technologies, and it can analyze large applications. Fortify takes a long time and may not be able to generate the report for larger applications. We don't have these constraints with Veracode.""I like the sandbox, the ability to upload compiled code, and how easy it is.""Veracode Fix is a new feature that functions similarly to auto-remediation for low or medium flaw codes.""The source composition analysis component is great because it gives our developers some comfort in using new libraries."

More Veracode Pros →

Cons
"GitHub Code Scanning should add more templates."

More GitHub Code Scanning Cons →

"The scanning is a little slow, but other than that it's fine. It's usually when the binaries get up into the multi-hundred megabyte size.""I would like Veracode to add more language support.""The security labs integration has room for improvement.""The ideal situation in terms of putting the results in front of the developers would be with Veracode integration into the developer environment (IDE). They do have a plugin, which we've used in the past, but we were not as positive about it.""The GUI requires significant simplification, as its current complexity creates a steep learning curve for new users.""There is much to be desired of UI and user experience. The UI is very slow. With every click, it just takes a lot of time for the pages to load. We have seen this consistently since getting this solution. The UI and UX are very disjointed.""The Greenlight product that integrates into the IDE is not available for PHP, which is our primary language.""The only areas that I'm concerned with are some of the newer code libraries, things that we're starting to see people dabble with. They move quickly enough to get them into the Analysis Engine, so I wouldn't even say it is a complaint. It is probably the only thing I worry about: Occasionally hitting something that is built in some other obscure development model, where we either can't scan it or can't scan it very well."

More Veracode Cons →

Pricing and Cost Advice
  • "GitHub Code Scanning is a moderately priced solution."
  • "The minimum pricing for the tool is five dollars a month."
  • More GitHub Code Scanning Pricing and Cost Advice →

  • "Its complexity makes it quite expensive, but it’s all worth it, with all the engineering in the background."
  • "The pricing is pretty high."
  • "The worst part about the product is that it does not scale at all. Also, microservices apps will cost you a fortune."
  • "I think licensing needs to be changed or updated so that it works with adjustments. Pricing is expensive compared to the amount of scanning we perform."
  • "It's worth the value"
  • "Pricing seems fair for what is offered, and licensing has been no problem. All developers are able to get the access they need."
  • "It can be expensive to do this, so I would just make sure that you're getting the proper number of licenses. Do your analysis. Make sure you know exactly what it is you need, going in."
  • "The licensing and prices were upfront and clear. They stand behind everything that is said during the commercial phase and during the onboarding phase. Even the most irrelevant "that can be done" was delivered, no matter how important the request was."
  • More Veracode Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Static Application Security Testing (SAST) solutions are best for your needs.
    772,649 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:We use GitHub Code Scanning mostly for source code management.
    Top Answer:GitHub Code Scanning is a moderately priced solution. On a scale from one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing a five out of ten. The solution's license is… more »
    Top Answer:GitHub Code Scanning should add more templates.
    Top Answer:SonarQube is easy to deploy and configure, and also integrates well with other tools to do quality code analysis. SonarQube has a great community edition, which is open-source and free. Easy to use… more »
    Top Answer:The SAST and DAST modules are great.
    Top Answer:The product’s price is a bit higher compared to other solutions. However, the tool provides good vulnerability and database features. It is worth the money.
    Ranking
    Views
    190
    Comparisons
    160
    Reviews
    1
    Average Words per Review
    337
    Rating
    10.0
    Views
    25,312
    Comparisons
    17,044
    Reviews
    101
    Average Words per Review
    989
    Rating
    8.1
    Comparisons
    Also Known As
    Crashtest Security , Veracode Detect
    Learn More
    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.

    Veracode is a global leader in Application Risk Management for the AI era. Powered by trillions of lines of code scans and a proprietary AI-generated remediation engine, the Veracode platform is trusted by organizations worldwide to build and maintain secure software from code creation to cloud deployment. Thousands of the world’s leading development and security teams use Veracode every second of every day to get accurate, actionable visibility of exploitable risk, achievereal-time vulnerability remediation, and reduce their security debt at scale. Veracode is a multi-award-winning company offering capabilities to secure the entire software development life cycle, including Veracode Fix, Static Analysis, Dynamic Analysis, Software Composition Analysis, Container Security, Application Security Posture Management, and Penetration Testing.

    Learn more atwww.veracode.com, on theVeracode blog, and onLinkedInandTwitter.

    Sample Customers
    Information Not Available
    Manhattan Associates, Azalea Health, Sabre, QAD, Floor & Decor, Prophecy International, SchoolCNXT, Keap, Rekner, Cox Automotive, Automation Anywhere, State of Missouri and others.
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company18%
    Financial Services Firm14%
    Media Company6%
    Comms Service Provider6%
    REVIEWERS
    Computer Software Company26%
    Financial Services Firm23%
    Insurance Company9%
    Comms Service Provider6%
    VISITORS READING REVIEWS
    Financial Services Firm18%
    Computer Software Company15%
    Manufacturing Company8%
    Government6%
    Company Size
    No Data Available
    REVIEWERS
    Small Business31%
    Midsize Enterprise20%
    Large Enterprise49%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise14%
    Large Enterprise69%
    Buyer's Guide
    GitHub Code Scanning vs. Veracode
    June 2024
    Find out what your peers are saying about GitHub Code Scanning vs. Veracode and other solutions. Updated: June 2024.
    772,649 professionals have used our research since 2012.

    GitHub Code Scanning is ranked 20th in Static Application Security Testing (SAST) with 2 reviews while Veracode is ranked 2nd in Static Application Security Testing (SAST) with 194 reviews. GitHub Code Scanning is rated 9.6, while Veracode is rated 8.2. The top reviewer of GitHub Code Scanning writes "A highly stable solution that can be used for source code management". On the other hand, the top reviewer of Veracode writes "Helps to reduce false positives and prevent vulnerable code from entering production, but does not support incremental scanning ". GitHub Code Scanning is most compared with SonarCloud, Coverity, SonarQube and Polaris Software Integrity Platform, whereas Veracode is most compared with SonarQube, Checkmarx One, Fortify on Demand, Snyk and Fortify Static Code Analyzer. See our GitHub Code Scanning vs. Veracode 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.