Helping developers ensure code quality and security with Coverity Scan

The problem: Ensuring open source code quality and security

“We integrated Coverity Scan into our CI/CD pipeline soon after establishing NGINX,” said Maxim Konovalov, one of the company’s cofounders and now VP of engineering. “We’ve been submitting NGINX build artifacts daily since 2012.”

“In many cases, NGINX acts as an internet front end,” continued Konovalov. “Its security and stability are essential to its users. My team is passionate about code quality and are always looking for best practices and tools to help us improve it. Static code analyzers such as Coverity Scan provide a great help to us.”

NGINX takes its role as a foundational technology to millions of apps and websites very seriously. Code quality and security are part of its ethos, and the tools that help support that mission are integral to its development practices.

The solution: Static code analysis with Coverity Static Analysis

Contrary to popular opinion, most software vulnerabilities are the result of coding mistakes, not malicious attacks. According to the “2020 State of the Octoverse” security report, 83% of the vulnerabilities that GitHub sent alerts on from 2019 through 2020 were due to coding errors rather than malicious intent.

But malicious attacks do exploit flaws in code, and developers need to embrace proactive detection tools to uncover bugs in the code they write. Static analysis examines source code against a set of coding rules to uncover common coding errors. A free service for open source developers who have registered their projects with scan.coverity.com, Coverity Scan is powered by the same engine used by Black Duck's commercial Coverity^® Static Analysis tool to help open source developers identify code defects for fast and easy remediation. A 2020 report from the Linux Foundation surveying open source contributors noted that respondents “overwhelmingly cited Coverity Scan and Clang security checkers” as the primary static analysis tools they use.

The results: 658,000 lines of code scanned with a defect density of 0.02%

In the January 2021 Coverity Scan of a NGINX build, 658,665 lines of code were analyzed, and various code defects uncovered, including two CWE Top 25 defects. Thanks to F5’s regular use of Coverity Scan, the NGINX project has a defect density (number of defects per 1,000 lines of code) of only 0.02%.

“Coverity Scan provides an invaluable service to us,” says Maxim Konovalov. “I regularly recommend Coverity Scan and its ability to provide specific defect IDs in code commits. And in fact, I’m a member of the FreeBSD committers group, and we use Coverity Scan for code analyses of FreeBSD as well.”