<commit_before><% @title = "Security" %>

<div class="l-colspan t-body">
  <p>
    Found a security issue with RubyGems or RubyGems.org?
    Please follow these steps to report it.
  </p>

  <h2>Reporting a security issue</h2>

  <p>
    Before continuing, please ensure this is a security issue for the RubyGems
    client or the RubyGems.org service. For all vulnerabilites with individual
    gems, follow our guide on <a href="http://guides.rubygems.org/security/#reporting-security-vulnerabilities">
      reporting security issues</a> with others' gems. If it's a security issue
    with the Ruby on Rails framework, see the <a href="http://rubyonrails.org/security/">
      Rails Security</a> guide.
  </p>

  <p>
    <strong>
      For any security bug or issue with the RubyGems client or
      RubyGems.org service, please email <a href="mailto:<EMAIL>">
        <EMAIL></a> with details about the problem.
    </strong>
  </p>

  <p>
    <small>
      Please note: the <a href="https://groups.google.com/forum/#!forum/rubygems-developers">
        rubygems-developers mailing list</a>, the
      <a href="https://groups.google.com/forum/#!forum/rubygems-org">rubygems.org
        mailing list</a>, and the <a href="ircs://irc.freenode.net:6697/#rubygems">
        #rubygems</a> IRC channel are public areas.

      If escalating to these places, please do not discuss your issue,
      simply say that you’re trying to get a hold of someone from the security
      team. Thanks in advance for responsibly disclosing your security issue.
    </small>
  </p>

  <h2>Your Security</h2>

  <h3>Securely pushing Gems</h3>
  <p>
    You may wish to <a href="http://guides.rubygems.org/security/#building-gems">
      sign your gems</a> before releasing them to RubyGems.org.
  </p>

  <h3>Securely downloading Gems</h3>
  <p>
    The SHA256hash provided with files on RubyGems.org exists only to provide some
    download corruption protection. It is not intended to provide any sort of
    security regarding tampering. Please use GPG signing for that.
  </p>

  <p>
    Also, see <a href="https://gist.github.com/bf4/4223e83e8becacfb2a8e">this gist</a>.
  </p>

  <h2>Reporting RubyGems.org Website Problems</h2>
  <p>
    If you're having trouble pushing a gem, or otherwise need help with your
    RubyGems.org account, please <a href="http://help.rubygems.org">
      open a new help issue</a>.
  </p>

  <p>
    For bugs or other problems with RubyGems.org, please use the
    <a href="https://github.com/rubygems/rubygems.org">RubyGems.org issue tracker</a>
    to open a new issue.
  </p>

  <h2>Disclosure Policy</h2>

  <p>
    RubyGems and RubyGems.org follow a 5 step disclosure policy:
  </p>

  <ol>
    <li>
      Security report received and is assigned a primary handler. This person
      will coordinate the fix and release process.
    </li><commit_msg>Ditch Your Security section for now, let's improve the guides instead and focus on reporting<commit_after><% @title = "Security" %>

<div class="l-colspan t-body">
  <p>
    Found a security issue with RubyGems or RubyGems.org?
    Please follow these steps to report it.
  </p>

  <h2>Reporting a security issue</h2>

  <p>
    Before continuing, please ensure this is a security issue for the RubyGems
    client or the RubyGems.org service. For all vulnerabilites with individual
    gems, follow our guide on <a href="http://guides.rubygems.org/security/#reporting-security-vulnerabilities">
      reporting security issues</a> with others' gems. If it's a security issue
    with the Ruby on Rails framework, see the <a href="http://rubyonrails.org/security/">
      Rails Security</a> guide.
  </p>

  <p>
    <strong>
      For any security bug or issue with the RubyGems client or
      RubyGems.org service, please email <a href="mailto:<EMAIL>">
        <EMAIL></a> with details about the problem.
    </strong>
  </p>

  <p>
    <small>
      Please note: the <a href="https://groups.google.com/forum/#!forum/rubygems-developers">
        rubygems-developers mailing list</a>, the
      <a href="https://groups.google.com/forum/#!forum/rubygems-org">rubygems.org
        mailing list</a>, and the <a href="ircs://irc.freenode.net:6697/#rubygems">
        #rubygems</a> IRC channel are public areas.

      If escalating to these places, please do not discuss your issue,
      simply say that you’re trying to get a hold of someone from the security
      team. Thanks in advance for responsibly disclosing your security issue.
    </small>
  </p>

  <h2>Reporting RubyGems.org Website Problems</h2>
  <p>
    If you're having trouble pushing a gem, or otherwise need help with your
    RubyGems.org account, please <a href="http://help.rubygems.org">
      open a new help issue</a>.
  </p>

  <p>
    For bugs or other problems with RubyGems.org, please use the
    <a href="https://github.com/rubygems/rubygems.org">RubyGems.org issue tracker</a>
    to open a new issue.
  </p>

  <h2>Disclosure Policy</h2>

  <p>
    RubyGems and RubyGems.org follow a 5 step disclosure policy:
  </p>

  <ol>
    <li>
      Security report received and is assigned a primary handler. This person
      will coordinate the fix and release process.
    </li>
{'fraction_non_alphanumeric': 0.11041069723018147, 'fraction_numerical': 0.007831900668576886, 'mean_word_length': 3.0494972931167825, 'pattern_counts': {'":': 0, '<': 113, '<?xml version=': 0, '>': 113, 'https://': 7, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4605031', 'n_tokens_mistral': 1727, 'n_tokens_neox': 1640, 'n_words': 589}