Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

OSPS-GV-04.01 fails when CODEOWNERS is missing even if the policy is documented elsewhere

未关闭
#514 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
security

调研方向

Locate the OSPS-GV-04.01 check and read how its CODEOWNERS file_exists step is evaluated. Review the policy language in GOVERNANCE.md, CONTRIBUTING.md, MAINTAINERS.md, and README, then determine how the check should recognize the required policy. Done means a missing CODEOWNERS file does not fail the check when the policy is documented elsewhere.

由索引模型根据 Issue 内容生成。

描述

module-baseline

OSPS-GV-04.01 (Maturity Level 3) reads:

While active, the project documentation MUST have a policy that code collaborators are reviewed prior to granting escalated permissions to sensitive resources.

The first step is file_exists on CODEOWNERS / .github/CODEOWNERS / docs/CODEOWNERS, so a project without a CODEOWNERS file fails immediately, even when GOVERNANCE.md or CONTRIBUTING.md contains exactly this policy. CODEOWNERS is also not a policy about reviewing collaborators before escalating their permissions; it assigns reviewers to paths.

Suggested direction: drop the CODEOWNERS presence step as a FAIL condition and look for the policy in the governance documents (GOVERNANCE.md, CONTRIBUTING.md, MAINTAINERS.md, README), with the final say from a judgment of that content.

主要语言
Python
星标
22
派生
27
平均合并
1 天 19 小时
30 天内合并 PR
39

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

darnitdevorg/darnit 的其他 Issue

查看 darnitdevorg/darnit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。