Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Klocwork is a static code analysis and SAST tool designed for languages such as C, C++, C#, Java, and JavaScript, effectively pinpointing software security, quality, and reliability concerns while supporting adherence to various compliance standards. Tailored for enterprise-level DevOps and DevSecOps environments, Klocwork is capable of scaling to accommodate projects of any magnitude, seamlessly integrating with complex systems and a variety of developer tools, while also facilitating control, collaboration, and comprehensive reporting across the organization. This capability has established Klocwork as a leading static analysis solution that maintains rapid development cycles while ensuring ongoing compliance with security and quality protocols. By utilizing Klocwork's static application security testing (SAST) within DevOps practices, users can identify and rectify security vulnerabilities early on, maintaining alignment with globally acknowledged security standards. Furthermore, Klocwork's integration with CI/CD tools, cloud services, containers, and machine provisioning simplifies the process of automated security testing, making it accessible and efficient for teams. As a result, organizations can enhance their overall software development lifecycle while reducing potential risks associated with security flaws.
Description
The Secure Programming Group at the University of Virginia's Department of Computer Science is responsible for the development and ongoing maintenance of Splint. David Evans leads the project and serves as its main developer. Memory bounds checking was created by David Larochelle. Significant contributions to Splint's development were also made by University of Virginia students, including Chris Barker, David Friedman, Mike Lanouette, and Hien Phan. Splint serves as the evolution of LCLint, a tool that originated from a collaborative research effort between the Massachusetts Institute of Technology and Digital Equipment Corporation's System Research Center. David Evans was also the chief designer and developer of LCLint. The initial concept for a static checking tool aimed at identifying discrepancies between LCL specifications and their C implementations came from John Guttag and Jim Horning. Their insights into the design and functionality proved invaluable, playing a crucial role in shaping both LCLint and its successor, Splint. Together, the team has fostered a robust environment for developing tools that enhance software reliability and security.
API Access
Has API
Yes
API Access
Has API
No
Screenshots View All
No images available
Integrations
C
Yes
C++
Yes
Akana API Platform
Yes
Amazon Web Services (AWS)
Yes
BlazeMeter
Yes
C#
Yes
Eclipse IDE
Yes
Incredibuild
Yes
Java
Yes
Jenkins
Yes
Integrations
C
Yes
C++
Yes
Akana API Platform
No
Amazon Web Services (AWS)
No
BlazeMeter
No
C#
No
Eclipse IDE
No
Incredibuild
No
Java
No
Jenkins
No
Pricing Details
No price information available.
Free Trial
Yes
Free Version
No
Pricing Details
No price information available.
Free Trial
No
Free Version
Yes
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Customer Support
Business Hours
Yes
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
Yes
Live Training (Online)
Yes
In Person
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Vendor Details
Company Name
Perforce
Founded
1995
Country
United States
Website
www.perforce.com/products/klocwork
Vendor Details
Company Name
University of Virginia
Founded
2007
Country
United States
Website
splint.org
Product Features
Static Application Security Testing (SAST)
Application Security
No
Dashboard
No
Debugging
No
Deployment Management
No
IDE
No
Multi-Language Scanning
No
Real-Time Analytics
No
Source Code Scanning
No
Vulnerability Scanning
No
Static Code Analysis
Analytics / Reporting
No
Code Standardization / Validation
No
Multiple Programming Language Support
No
Provides Recommendations
No
Standard Security/Industry Libraries
No
Vulnerability Management
No
Product Features
Static Application Security Testing (SAST)
Application Security
No
Dashboard
No
Debugging
No
Deployment Management
No
IDE
No
Multi-Language Scanning
No
Real-Time Analytics
No
Source Code Scanning
No
Vulnerability Scanning
No
Static Code Analysis
Analytics / Reporting
No
Code Standardization / Validation
No
Multiple Programming Language Support
No
Provides Recommendations
No
Standard Security/Industry Libraries
No
Vulnerability Management
No