Start copying here:
| This rule was developed in part by Fatima Nadeem at the October 20-22, 2017 OurCS Workshop (http://www.cs.cmu.edu/ourcs/register.html). For more information about this statement, see the About the OurCS Workshop page. | 
|---|
End copying here.
| This guideline is under construction. | 
When having unreachable code it allows programs to be vulnerable to attacks and threat, as discovered "Understanding the Origins of Mobile App Vulnerabilities: A Large-scale Measurement Study of Free and Paid Apps".
Thus when creating new libraries or functions...
This noncompliant code example shows an a line of code that is unreachable.
| int x = 1;
 
if (x == 1){
	return x;
	x += 1;  
} | 
The statement following the return statement will never get executed thus created errors and bugs in the program which rely on that statement.
In this compliant solution with reachable code.
| int x = 1;
if (x == 1){
	x += 1;
	return x; 
}
 | 
Summary of risk assessment.
| Rule | Severity | Likelihood | Remediation Cost | Priority | Level | 
|---|---|---|---|---|---|
| TBD | Medium | Probable | Medium | 
 | 
 | 
Tools are available online, such as ProGuard, that help clean up code by removing unused statements that may have been a result of unreachable code.
| Tool | Version | Checker | Description | 
|---|---|---|---|
| TBD | 
 | 
Fill in the table below with at least one entry row, per these instructions, then remove this purple-font section.
| DRD10-X. Do not release apps that are debuggable | Issues of bugs and discrepency within the code relates to this rule. | 
| [TBD] |