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 摘要。