-
-
Notifications
You must be signed in to change notification settings - Fork 50
Added a basic SECURITY.md #3798
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.
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
Conversation
""" WalkthroughA new SECURITY.md file has been introduced to the repository. This document outlines the project's security policies, including procedures for reporting vulnerabilities, the maintainers' response process, and channels for community feedback regarding security matters. Changes
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (3)
SECURITY.md (3)
1-4
: Expand the Introduction to define policy scope
Consider adding a brief overview of the policy’s scope—what components or modules it covers, who it applies to (e.g., core maintainers, third-party contributors), and any exclusions. This helps set clear expectations for both reporters and responders.
11-12
: Clarify advisory publication timeline
Specify when and how advisories will be published (for example, “within 30 days of resolution” or “after CVE assignment”) and any embargo periods. This transparency builds trust and sets clear reporting-to-publication expectations.
13-16
: Minor formatting and metadata suggestions
- Ensure the file ends with a blank newline for POSIX compliance.
- Consider adding a “Last Updated” date or version identifier at the bottom for future maintenance.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
SECURITY.md
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Test
- GitHub Check: Release build
- GitHub Check: Query Performance Test
We should have had this file for a while, it gets displayed in the "Security" tab when present.
Summary by CodeRabbit