deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[PR #255] [CLOSED] Add SECURITY.md for vulnerability reporting policy #320

New issue
Closed
opened 2026-10-26 21:16:14 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-26 21:16:14 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/255
Author: @yurekami
Created: 12/25/2025
Status: ❌ Closed

Base: main ← Head: add-security-policy

📝 Commits (1)

  • 3eb7648 Add SECURITY.md for vulnerability reporting policy

📊 Changes

1 file changed (+61 additions, -0 deletions)

View changed files

➕ SECURITY.md (+61 -0)

📄 Description

Summary

Add a security policy document (SECURITY.md) to provide clear guidance for reporting vulnerabilities.

Contents:

  • Supported Versions: Clear table showing 2.x.x is supported
  • Reporting Instructions: How to report vulnerabilities privately (GitHub Security Advisories)
  • Response Timeline: 48h acknowledgment, 7-day updates, priority for critical issues
  • Scope: What's covered (library code, scripts) and what's not (dependencies, third-party)
  • Best Practices: Security considerations for JIT compilation, env vars, CUDA

Benefits

  • Enables GitHub's security features (private vulnerability reporting)
  • Provides clear expectations for security researchers
  • Demonstrates commitment to security
  • Standard practice for open source projects

Test plan

  • Markdown renders correctly
  • Links are valid
  • Verify GitHub Security tab shows the policy after merge

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/DeepGEMM/pull/255 **Author:** [@yurekami](https://github.com/yurekami) **Created:** 12/25/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-security-policy` --- ### 📝 Commits (1) - [`3eb7648`](https://github.com/deepseek-ai/DeepGEMM/commit/3eb7648a1e08f7d65c048c0917c429e1f2b37a50) Add SECURITY.md for vulnerability reporting policy ### 📊 Changes **1 file changed** (+61 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `SECURITY.md` (+61 -0) </details> ### 📄 Description ## Summary Add a security policy document (`SECURITY.md`) to provide clear guidance for reporting vulnerabilities. ### Contents: - **Supported Versions**: Clear table showing 2.x.x is supported - **Reporting Instructions**: How to report vulnerabilities privately (GitHub Security Advisories) - **Response Timeline**: 48h acknowledgment, 7-day updates, priority for critical issues - **Scope**: What's covered (library code, scripts) and what's not (dependencies, third-party) - **Best Practices**: Security considerations for JIT compilation, env vars, CUDA ### Benefits - Enables GitHub's security features (private vulnerability reporting) - Provides clear expectations for security researchers - Demonstrates commitment to security - Standard practice for open source projects ## Test plan - [x] Markdown renders correctly - [x] Links are valid - [ ] Verify GitHub Security tab shows the policy after merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 21:16:14 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
public-sync-20261014
0930-release
nv_dev
fix-mega-moe-fence
public-release-2609
public-release-2607
public-release-2606
mega-update
public-release-260416
ko3n1g/ci/build-wheels
nv_dev_f8e8fb5
nv_dev_950d31a
nv_dev_67fc648
nv_dev_c491439
nv_dev_4ff3f54
v2.1.1.post3
v2.1.1.post2
v2.1.1.post1
v2.1.1
v2.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepGEMM#320
No description provided.