docs: add security policy and advisory issue template#6
Merged
Conversation
Adds SECURITY.md with responsible disclosure process, supported versions, coordinated disclosure timeline, and supply-chain guidance for consumers. Adds a GitHub issue template for post-disclosure public advisories and updates the issue template config with a private reporting contact link. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a repository security policy and issue-template wiring to guide responsible vulnerability disclosure and reduce accidental public reporting.
Changes:
- Introduces
SECURITY.mdwith supported-versions guidance, private reporting channels, and coordinated disclosure expectations. - Adds a public “Security Advisory” issue form intended for post-disclosure discussion (after CVE/advisory publication).
- Updates issue template configuration to surface a private “Security Vulnerability” contact link in the issue picker.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| SECURITY.md | Adds a security policy document covering reporting channels, timelines, scope, and consumer guidance. |
| .github/ISSUE_TEMPLATE/security_advisory.yml | Adds an issue form for post-disclosure public discussions of already-published advisories/CVEs. |
| .github/ISSUE_TEMPLATE/config.yml | Adds a private security advisory contact link to the new-issue picker. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+75
to
+76
| - Verify the PyPI release signature via `sigstore` (signatures are attached to | ||
| each GitHub release). |
Relocates SECURITY.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md from the repository root to .github/ following the industry-standard layout for open-source projects. README.md, LICENSE, and CHANGELOG.md remain at root. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
Author
|
@copilot apply changes based on the comments in this thread |
Agent-Logs-Url: https://github.com/aseguragonzalez/python-seedwork/sessions/2f152160-3527-4e8a-aa0e-9ded5309cac9 Co-authored-by: aseguragonzalez <2671340+aseguragonzalez@users.noreply.github.com>
Contributor
Implemented in commit cbcbd0f. I updated |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SECURITY.mdfollowing GitHub's recommended security policy format and Google Project Zero's 90-day coordinated disclosure standard. Covers: supported versions, two private reporting channels (GitHub Security Advisories + email), response SLAs, coordinated disclosure steps (GHSA → CVE → CHANGELOG), scope definition, and supply-chain best practices for consumers..github/ISSUE_TEMPLATE/security_advisory.yml— a public issue template gated behind a prominent warning. Intended only for post-disclosure discussion after a CVE is already published, preventing accidental public exposure of live vulnerabilities..github/ISSUE_TEMPLATE/config.ymlto surface the private Security Advisories link directly in the "New Issue" picker, reducing the friction of responsible disclosure.Test plan
SECURITY.mdrenders correctly on GitHub and all links resolve.security_advisory.ymltemplate appears in the issue picker with the warning banner visible.Security → Policy) so GitHub links toSECURITY.mdautomatically.🤖 Generated with Claude Code