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

create_security_policy fails on every call; its template parameter is ignored

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with tests/darnit_baseline/test_tools_signatures.py and inspect the create_security_policy tool and the control template it uses. The issue leaves a choice between implementing the standard, minimal, and enterprise TOML variants or removing the pinned parameter. Done means the parameter is honored or removed consistently, while the existing SECURITY.md behavior remains unchanged.

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

描述

interface-mcp module-baseline needs triage

On main (0581c0d), the create_security_policy MCP tool fails on every call. It passes an EffectiveConfig to FrameworkConfig(**...), which raises. When it did produce output, it also reported "Created" when SECURITY.md already existed.

Fixed on the 043 branch: the tool runs OSPS-VM-02.01 through the remediation executor and the run manifest, never overwrites an existing SECURITY.md (it reports unchanged / already_exists), and returns the structured run.

Still open on the branch: the template parameter (standard / minimal / enterprise) is accepted but ignored; every call renders the control's own template. Either implement the variants as TOML templates selected by the parameter, or remove the parameter (it is pinned by tests/darnit_baseline/test_tools_signatures.py).

Found while implementing feature 043 (remediation safety, branch 043-remediation-safety, not yet merged).

主要语言
Python
星标
22
派生
27
平均合并
2 天 18 小时
30 天内合并 PR
51

环境准备

从这里开始

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

darnitdevorg/darnit 的其他 Issue

查看 darnitdevorg/darnit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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