Best Static Application Security Testing (SAST) Software for MATLAB
View:
Compare the Top Static Application Security Testing (SAST) Software that integrates with MATLAB as of June 2025
Sort By:
This a list of Static Application Security Testing (SAST) software that integrates with MATLAB. Use the filters on the left to add additional filters for products that have integrations with MATLAB. View the products that work with MATLAB in the table below.
What is Static Application Security Testing (SAST) Software for MATLAB?
Static Application Security Testing (SAST) software analyzes the source code, binaries, or bytecode of an application to identify vulnerabilities before the code is run in production. This type of software scans the application at rest to detect issues such as coding errors, security flaws, and weaknesses like SQL injection, cross-site scripting (XSS), and buffer overflows. SAST tools provide developers with early insights into potential security vulnerabilities, allowing them to fix issues before deployment. These tools are typically integrated into the software development lifecycle (SDLC), supporting secure coding practices and helping teams build more secure applications. Compare and read user reviews of the best Static Application Security Testing (SAST) software for MATLAB currently available using the table below. This list is updated regularly.
-
1
Splint
University of Virginia
Splint is developed and maintained by the Secure Programming Group at the University of Virginia Department of Computer Science. David Evans is the project leader and the primary developer of Splint. David Larochelle developed the memory bounds checking. University of Virginia students Chris Barker, David Friedman, Mike Lanouette and Hien Phan all contributed significantly to the development of Splint. Splint is the successor to LCLint, a tool originally developed as a joint research project between the Massachusetts Institute of Technology and Digital Equipment Corporation's System Research Center. David Evans was the primary designed and developer of LCLint. John Guttag and Jim Horning had the original idea for a static checking tool for detecting inconsistencies between LCL specifications and their C implementations. They provided valuable advice on its functionality and design and were instrumental in its development.
- Previous
- You're on page 1
- Next