anchor.diff:    <strong><%= @project.static_analysis_common_vulnerabilities_status %>:</strong>
     It is SUGGESTED that the tool include rules or approaches to look for
     common vulnerabilities in the analyzed language or environment.
  -  [static-analysis-common-vulnerabilities]
  +  <sup>[static-analysis-common-vulnerabilities]</sup>
     <!-- static_analysis_common_vulnerabilities_justification -->
   </p>
   
  
positive.code:   <strong><%= @project.static_analysis_fixed_status %>:</strong>
    All confirmed medium and high severity exploitable vulnerabilities discovered
    with static code analysis MUST be fixed. A vulnerability is medium to high
    severity if its CVSS 2.0 is 4 or higher. [static-analysis-fixed]
    <!-- static_analysis_fixed_justification -->
  </p>
  
  <p>
    <strong><%= @project.static_analysis_often_status %>:</strong>
    It is SUGGESTED that static source code analysis occur on every commit or at least daily.
    [static-analysis-often]
    <!-- static_analysis_often_justification -->
  </p>
  
  
negative.code:   <strong><%= @project.crypto_published_status %>:</strong>
    Cryptographic protocols and algorithms used by default in the software AND
    the delivery mechanisms MUST be publicly published and reviewed by experts.
    <sup>[crypto-published]</sup>
    <!-- crypto_published_justification -->
  </p>
  
  