Developer experience · Empirical predictive/observational study
Evaluating Complexity, Code Churn, and Developer Activity Metrics as Indicators of Software Vulnerabilities
IEEE Transactions on Software Engineering · 2011
Summary
Evaluates complexity, churn, and developer-activity measures as indicators of vulnerable code.
For your marketing
Possible founder application
Use churn and ownership signals to focus security review, while validating against actual vulnerability outcomes.
Reported result
What the study found
Evaluates complexity, churn, and developer-activity measures as indicators of vulnerable code.
Research question
What the authors investigated
How does the study’s stated design explain its reported outcome in this setting?
Design
Empirical predictive/observational study
Sample and setting
Software repositories and vulnerability data; abstract-only
Scope and transfer
Limitations to keep in view
Repository-based indicators can be confounded by project, language, and process differences.
Research sources
abstract_only