[GH-ISSUE #70] Coverity Scan #52

Closed
opened 2026-02-26 10:35:26 +03:00 by kerem · 2 comments
Owner

Originally created by @AlexLaroche on GitHub (Nov 14, 2014).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/70

Originally assigned to: @Pro on GitHub.

What is static analysis?

Static analysis is a set of processes for finding source code defects and vulnerabilities.

In static analysis, the code under examination is not executed. As a result, test cases and specially designed input datasets are not required. Examination for defects and vulnerabilities is not limited to the lines of code that are run during some number of executions of the code, but can include all lines of code in the codebase.

Additionally, Coverity's implementation of static analysis can follow all the possible paths of execution through source code (including interprocedurally) and find defects and vulnerabilities caused by the conjunction of statements that are not errors independent of each other.

https://scan.coverity.com/travis_ci

Originally created by @AlexLaroche on GitHub (Nov 14, 2014). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/70 Originally assigned to: @Pro on GitHub. What is static analysis? Static analysis is a set of processes for finding source code defects and vulnerabilities. In static analysis, the code under examination is not executed. As a result, test cases and specially designed input datasets are not required. Examination for defects and vulnerabilities is not limited to the lines of code that are run during some number of executions of the code, but can include all lines of code in the codebase. Additionally, Coverity's implementation of static analysis can follow all the possible paths of execution through source code (including interprocedurally) and find defects and vulnerabilities caused by the conjunction of statements that are not errors independent of each other. https://scan.coverity.com/travis_ci
kerem 2026-02-26 10:35:26 +03:00
Author
Owner

@Pro commented on GitHub (Nov 14, 2014):

Done: https://scan.coverity.com/projects/3482/view_defects
To trigger a new coverity scan, we need to push to the coverity_scan branch

<!-- gh-comment-id:63049161 --> @Pro commented on GitHub (Nov 14, 2014): Done: https://scan.coverity.com/projects/3482/view_defects To trigger a new coverity scan, we need to push to the `coverity_scan` branch
Author
Owner

@AlexLaroche commented on GitHub (Nov 14, 2014):

Thanks.

<!-- gh-comment-id:63051325 --> @AlexLaroche commented on GitHub (Nov 14, 2014): Thanks.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#52
No description provided.