Secure Coding — Top 15 Code Analysis Tools - Security Boulevard

Secure Coding — Top 15 Code Analysis Tools

Keeping code secure is a top objective for any software company. And to ensure secure coding, you need to perform code analysis during the development life cycle.

While manual review of code was once the only option, now there are plenty of tools that can take care of this in an automated fashion. This is referred to as static code analysis, and the technique works quickly, scanning each line of code to identify any security flaws or gaps.

The use of code analysis tools offers many advantages. Automation saves time and resources so that coders can focus on other aspects during the life cycle. By adopting static code analysis procedures, organizations can ensure they are delivering secure and reliable software. By implementing the process early, security issues are found sooner and resolved.

Let’s look at 15 code analysis tools, their capabilities and why they might be something you’ll want to use.

The Top 15


  • Open-source
  • Works with C++, C#, VB, PHP, Java and PL/SQL
  • Tracks insecurities in code

VisualCodeGrepper is a must-use tool because it works fast, so if you don’t have a lot of time, it can be a lifesaver. Plus, it has a config file for each language that allows users to add bad functions for which to search. At the end of the scan, you’ll get a handy pie chart showing what the scan found.

Download it here.


  • Open-source
  • Works with C, C++, C#, Objective-C, Java, JavaScript, node JS, Ruby, PHP and Python
  • Supports 100 compilers
  • Delivers a clear description of root causes of code issues
  • Vulnerabilities scanned for include resources leaks, NULL pointers, incorrect usage of APIs, use of uninitialized data, memory corruptions, buffer overruns, control flow, error handling, concurrency, insecure data, unsafe use of signed values and use of resources that have been (Read more...)

*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Beth Osborne. Read the original post at: