Software Resiliency

Definition

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

 

Thresholds

Thresholds used for Software Resiliency categories:

  • Low/Red:¬†below 65.0
  • Medium/Orange:¬†from 65.0 to 87.0
  • High/Green:¬†above 87.0

 

Code Insights

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

Use of ‘return’ statement is not recommended
Read more
Do not compare to null
Read more
phpinfo() should not be used in production
Read more
The code contains too many PHP4 deprecated constructor naming.
Read more
The code contains too many final artifacts in final classes
Read more
The code contains too many classes that declare __get() without declaring __set()
Read more
Force casts should not be used
Read more
Avoid abstract classes without abstract or concrete methods
Read more
Variables should be declared with ‘let’ or ‘const’
Read more
Multiline string literals should not be used
Read more
Logical OR should not be used in switch cases
Read more
Avoid caching selector for long time
Read more
URIs (URL & path) should not be hardcoded for testability purpose
Read more
try! should not be used
Read more
Avoid generic catch
Read more
Avoid undefined type on data or routines declaration
Read more
Avoid to update static fields from instance methods
Read more
Avoid Public finalize() methods
Read more
Avoid confusing initialization for variables declared on the same line
Read more
The code contains too many unnecessary COMPUTE
Read more