Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future: Consider adding static analysis for vulnerabilities (e.g., hit density) #27

Open
david-a-wheeler opened this issue Jul 22, 2015 · 2 comments

Comments

@david-a-wheeler
Copy link
Contributor

Per section 5.B of the paper:

Perform static analysis on source code to determine the likely number of latent vulnerabilities (e.g., using Coverity scan, RATS, or flawfinder); measures such as hit density could indicate more problematic software. A variant would be to report on densities of warnings when warning flags are enabled.

@ya1gaurav
Copy link

This will report many False Alarms.

@david-a-wheeler
Copy link
Contributor Author

Sure, but the point would be to see if the density was unusually high. If you keep walking to the edge of a cliff, eventually you are likely to fall off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants