Add SECURITY.md and enable secret scanning (missing on 3 of 4 OSE repos)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 50/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github, markdown
调研方向
Start by reading the disclosure path in qBraid/qBraid's SECURITY.md, then add a SECURITY.md at the root of pyqasm, qbraid-qir and qbraid-algorithms, which currently have none. Each file should name a contact and a response expectation. Secret scanning and push protection are toggled under the repository's Settings, in the code security section. Done means all three repositories have a SECURITY.md and both settings are enabled where they were off.
由索引模型根据 Issue 内容生成。
描述
Problem
Three of the four public OSE repositories have no SECURITY.md, so a researcher who finds a vulnerability in them has no documented private disclosure path. Their only options are a public issue, which discloses the problem to everyone at once, or guessing at an email address.
| Repo | SECURITY.md |
Secret scanning |
|---|---|---|
qBraid |
✅ | ✅ enabled |
pyqasm |
❌ | ❌ disabled |
qbraid-qir |
❌ | ❌ disabled |
qbraid-algorithms |
❌ | ❌ disabled |
PyQASM is the sharpest case: it now records more monthly downloads than the qBraid-SDK, so it is the most-installed package in the ecosystem and the one with no way to report a vulnerability privately.
Suggested fix
- Add
SECURITY.mdtopyqasm,qbraid-qirandqbraid-algorithms, pointing at the same disclosure pathqBraid/qBraidalready uses. A short file naming a contact and a response expectation is enough. - Enable secret scanning and push protection on the three repositories where they are off. Both are settings changes.
- Consider enabling private vulnerability reporting so reports arrive through GitHub rather than email.
Why now
Zero security advisories have been published across all four repositories in the project's history. That reflects no reported vulnerabilities rather than a process for handling them, and the first report is a bad time to discover the process does not exist.
- 主要语言
- Python
- 星标
- 29
- 派生
- 33
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 15
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
qBraid/pyqasm 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
enhancement error-handling program-validation
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Move the QASM 2 printer and its branch pre-processing out of qasm2.py可能已有人在做 @danielgaskins 于 7 天前认领。 未关闭enhancement qasm2
难度 4/5 3-5 天 新手友好度 22/100
维护者通常 1 天内回复
-
[BUG] dumps() emits extern calls without a semicolon, producing unparsable QASM可能已有人在做 @Jah-yee 于 15 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 25/100
维护者通常 1 天内回复
-
Parse failures raise ValidationError with an empty message; the ANTLR diagnostic is lost可能已有人在做 @tonycoder-hub 于 9 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 22/100
维护者通常 1 天内回复
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
anchore/grype-db#1149 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: `hermes plugins update` clones an entire monorepo twice - `subdir` is resolved but dropped at both catalog-update call sites可能已有人在做 @HootRock 今天认领。 未关闭comp/cli P2 type/perf
难度 2/5 1-3 小时 新手友好度 72/100
NousResearch/hermes-agent#142417 · 2 条评论 ·
维护者通常 1 天内回复
-
SMC SPEC
难度 2/5 1-3 小时 新手友好度 70/100
tenstorrent/tt-oca-harness#3287 ·
维护者通常 1 天内回复
-
bug enhancement python
难度 2/5 1-3 小时 新手友好度 85/100
DewaldOosthuizen/tech-cheat-sheets-and-notes#392 ·
维护者通常 1 天内回复
-
security
难度 2/5 1-3 小时 新手友好度 72/100
fabriziosalmi/wildbox#801 ·
维护者通常 1 天内回复