Skip to content

Add SECURITY.md with policy for private security reports #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dwnoble wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add SECURITY.md with policy for private security reports #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Security Policy

## Reporting a Vulnerability

Please report any security vulnerabilities by emailing us at [support@datacommons.org](mailto:support@datacommons.org). Please do not open a public issue or pull request.

@gemini-code-assist gemini-code-assist Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

It is highly recommended to set expectations for security researchers by including a response timeline (e.g., acknowledging the report within 48 hours). This encourages responsible disclosure and establishes clear communication.

Suggested change
Please report any security vulnerabilities by emailing us at [support@datacommons.org](mailto:support@datacommons.org). Please do not open a public issue or pull request.
Please report any security vulnerabilities by emailing us at [support@datacommons.org](mailto:support@datacommons.org). Please do not open a public issue or pull request. We will acknowledge receipt of your report within 48 hours and keep you updated on the progress of our investigation.


### What to Include in the Report

To help us address the issue as quickly as possible, please include the following details in your report:
- A description of the vulnerability and its potential impact.
- Step-by-step instructions (or a proof-of-concept script) to reproduce the issue.
- Any details about the environment or configuration where the issue was found.

We appreciate your help in keeping Data Commons secure!