Software Resiliency

Definition

Software Resiliency indicates programming best practices that make software bullet-proof, more robust and secure. This index is derived through technology-specific code analysis that searches for the presence of code patterns and bad programming practices that may comprise the reliability of the software at short term. Higher is the Software Resiliency, lower is the likelihood of defects occurring in production.

 

Thresholds

Thresholds used for Software Resiliency categories:

  • High (green): value > 84.0
  • Medium (orange): value >= 62.0
  • Low (red): value < 62.0

 

Code Insights

Find below some code insight examples which contribute to the Software Resiliency index.

Top Level Functions declaring Too Many Functions is a Risk
Read more
Spaces between function name and opening parenthesis cause bugs
Read more
Builtin instructions are inadvisable because of their risky nature
Read more
Deep functions are a Production Risk in JavaScript
Read more
Suspicious File Usage patterns can be risky
Read more
File Records with no COPY Clause can be risky
Read more
EVALUATE instructions without default treatment causes Production Risk
Read more
Standard SQL API increases Production Risk in JSP
Read more
TLD Headers can reduce Production Risks
Read more
Break Statements helps reduce production risk
Read more
Magic Numbers are a Production Risk
Read more
% operator to format string can cause production risk
Read more
Whitespaces are a Production Risk
Read more
String concatenation in loop causes production risks
Read more
Java-Style getters and setters can increase production risks
Read more
Wildcard(*) imports can increase production risks.
Read more
Illegal exceptions can cause Production Risks
Read more
Handling Exceptions should be explicit
Read more
While Loops are more productive than For Loops
Read more
Constructors with a return value can be unproductive in PHP
Read more