Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Security Policy

If you discover a security vulnerability in bundler-audit, please report it
privately.

## Reporting A Vulnerability

- Email: postmodern.mod3@gmail.com

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we need to change the email now. Any idea where to point now? @jasnow what about your contact?

@jasnow jasnow May 31, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened this yesterday for security@rubysec.com:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to propose that we use a contact address that is itself a resource with shared ownership (e.g., a private Google group where we can manage membership and permissions), presuming we gain control of gem publishing.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resource with shared ownership (e.g., a private Google group where we can manage
membership and permissions), presuming we gain control of gem publishing.
My previous thoughts are in ISS #428 but I can support @flavorjones' approach too.

- Subject: "[bundler-audit] Security vulnerability report"

Please include:

- A clear description of the issue and impact.
- Steps to reproduce or a proof of concept.
- Affected versions and environment details.
- Any suggested remediation, if known.

Do not open a public GitHub issue for suspected vulnerabilities.

## Encryption

If you want to send encrypted details, mention this in your initial email and we
will coordinate a secure channel.

## Disclosure Process

After confirmation, maintainers will:

1. Acknowledge receipt.
2. Investigate and validate the report.
3. Prepare and release a fix.
4. Coordinate responsible disclosure details.
22 changes: 22 additions & 0 deletions spec/security_policy_spec.rb
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
require 'spec_helper'

describe 'SECURITY.md' do
let(:path) do
File.expand_path(File.join(File.dirname(__FILE__), '..', 'SECURITY.md'))
end

let(:content) { File.read(path) }

it 'exists' do
expect(File.file?(path)).to be(true)
end

it 'contains private reporting guidance' do
expect(content).to include('Reporting A Vulnerability')
expect(content).to include('Do not open a public GitHub issue')
end

it 'contains a security contact channel' do
expect(content).to include('postmodern.mod3@gmail.com')
end
end