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

Add benign and malicious corpus with false-positive and redaction policy

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
security, testing

调研方向

Start by reviewing dependency #28 and the roadmap item B06-02, then agree on the corpus composition and redaction and confidence policy at the decision gate. Build benign and malicious fixtures with expected outcomes, and record true positives, false positives, and misses per rule. Done means false-positive rates are recorded and reports redact secret-like values while retaining paths and confidence.

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

描述

status:approved type:chore

Goal

Add a benign and malicious corpus and data fixtures that measure false positives and enforce secret redaction with a paths and confidence policy.

Observations

  • Detection quality needs measurement, not assertion.
  • Findings may reference sensitive content and must be redacted.
  • Paths and confidence need a documented policy.

Decision gate

Approve corpus composition and the redaction and confidence policy before wiring assertions.

Acceptance criteria

  • Benign and malicious corpora exist with expected outcomes.
  • False-positive rate is measured and recorded per rule.
  • Redaction hides secret-like content while keeping paths and confidence.

Verification

  • Corpus run -> recorded true positives, false positives, and misses per rule.
  • Redaction check -> secret-like values absent from reports, paths retained.

Release checkpoint

Remaining risk: a corpus is a sample, not proof of completeness. No unconditional LLM verdicts.

Tracking

Roadmap item: B06-02. All acceptance criteria remain pending; publication does not grant approval or release authority.

Dependencies

  • Depends on #28 (B06-01).
主要语言
JavaScript
星标
22
派生
3
平均合并
27 分钟
30 天内合并 PR
27

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

egdev6/github-repository-bootstrap 的其他 Issue

查看 egdev6/github-repository-bootstrap 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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