<commit_before><% content_for :nav_progress do %>
<div class="progress">
  <div id="badge-progress" class="progress-bar progress-bar-success" role="progressbar" aria-valuenow="0" aria-valuemin="0" aria-valuemax="100" style="width: 0%; min-width: 2em;">0%</div>
</div>
<% end %>

<div class="row">
<div class="col-md-12">

<span id="project_entry_form"></span>

<div class="text-center hidden-print">
<button id="show-all-details" class="btn" title="Show all detailed text" type="button">Show all detailed text</button>
|
<button id="hide-all-details" class="btn" title="Hide all detailed text" type="button">Hide all detailed text</button>
</div>
<div class="hidden">
<%= image_tag "Thumbs_up_font_awesome.svg", id: "Thumbs_up_img" %>
<%= image_tag "Thumbs_down_font_awesome.svg", id: "Thumbs_down_img" %>
</div>

<br>
<p>
Open source software (OSS) projects
that follow the best practices below
will be able to voluntarily self-certify and show that they've
achieved a Core Infrastructure Initiative (CII) badge.
<%= render(partial: "details", locals: {
           criteria: "badge_intro", details: %{
There is no set of practices that can guarantee that software
will never have defects or vulnerabilities.
However, following best practices can help improve the results
of OSS projects.
We plan to improve the page design later; for now, please focus on
the criteria and how they're combined.
To earn a badge the current rules are:
<ul>
<li>all MUST and MUST NOT criteria must be met,<commit_msg>Make it clear that you should 'submit' often, and can edit more later.<commit_after><% content_for :nav_progress do %>
<div class="progress">
  <div id="badge-progress" class="progress-bar progress-bar-success" role="progressbar" aria-valuenow="0" aria-valuemin="0" aria-valuemax="100" style="width: 0%; min-width: 2em;">0%</div>
</div>
<% end %>

<div class="row">
<div class="col-md-12">

<span id="project_entry_form"></span>

<div class="text-center hidden-print">
<button id="show-all-details" class="btn" title="Show all detailed text" type="button">Show all detailed text</button>
|
<button id="hide-all-details" class="btn" title="Hide all detailed text" type="button">Hide all detailed text</button>
</div>
<div class="hidden">
<%= image_tag "Thumbs_up_font_awesome.svg", id: "Thumbs_up_img" %>
<%= image_tag "Thumbs_down_font_awesome.svg", id: "Thumbs_down_img" %>
</div>

<br>
<p>
Open source software (OSS) projects
that follow the best practices below
will be able to voluntarily self-certify and show that they've
achieved a Core Infrastructure Initiative (CII) badge.
<% if (!is_disabled) %>
<b>Please 'submit' often</b> to save your work
(you can always go back and edit more later).
<% end %>
<%= render(partial: "details", locals: {
           criteria: "badge_intro", details: %{
There is no set of practices that can guarantee that software
will never have defects or vulnerabilities.
However, following best practices can help improve the results
of OSS projects.
We plan to improve the page design later; for now, please focus on
the criteria and how they're combined.
To earn a badge the current rules are:
<ul>
<li>all MUST and MUST NOT criteria must be met,
{'fraction_non_alphanumeric': 0.1349056603773585, 'fraction_numerical': 0.006289308176100629, 'mean_word_length': 5.58592132505176, 'pattern_counts': {'":': 0, '<': 57, '<?xml version=': 0, '>': 55, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4114777', 'n_tokens_mistral': 1041, 'n_tokens_neox': 980, 'n_words': 360}