anchor.diff:    <strong><%= @project.crypto_oss_status %>:</strong>
     All functionality that depends on cryptography MUST be implementable using
     OSS because its specification meets the Open Standards Requirement for
  -  Software by the Open Source Initiative [crypto-oss]
  +  Software by the Open Source Initiative <sup>[crypto-oss]</sup>
     <!-- crypto_oss_justification -->
   </p>
   
  
positive.code:   <strong><%= @project.description_sufficient_status %>:</strong>
    The project website MUST succinctly describe what the software does
    (what problem does it solve?), in language that potential users can understand (e.g., it uses minimal jargon).
    [description-sufficient]
    <!-- description_sufficient_justification -->
  </p>
  
  <p>
    <strong><%= @project.interact_status %>:</strong>
    The project website MUST provide information on how to: obtain, provide feedback
    (as bug reports or enhancements), and contribute to the sofware. [interact]
    <!-- interact_justification -->
  </p>
  
  <p>
    <strong><%= @project.contribution_status %>:</strong>
    The information on how to contribute MUST explain the contribution process
    (e.g., are pull requests used?) [contribution]
    <!-- contribution_justification -->
  </p>
  
  
negative.code:   because speed is vital). Examples of such static code analysis tools include cppcheck,
    the clang static analyzer, FindBugs (including FindSecurityBugs), PMD, Brakeman,
    Coverity Quality Analyzer, and the HP Fortify Static Code Analyzer.
    <sup>[static-analysis]</sup>
    <!-- static_analysis_justification -->
  </p>
  
  