Add benign and malicious corpus with false-positive and redaction policy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
Research direction
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.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 3
- Avg merge
- 27m
- Merged PRs (30d)
- 27
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from egdev6/github-repository-bootstrap
-
status:approved type:chore
Difficulty 5/5 Over a week Newbie friendliness 25/100
egdev6/github-repository-bootstrap#57 ·
Maintainers usually reply within 1 day
-
type:docs
Difficulty 1/5 Under an hour Newbie friendliness 20/100
egdev6/github-repository-bootstrap#50 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
egdev6/github-repository-bootstrap#49 ·
Maintainers usually reply within 1 day
-
status:approved type:chore
Difficulty 5/5 Over a week Newbie friendliness 25/100
egdev6/github-repository-bootstrap#30 ·
Maintainers usually reply within 1 day
-
enhancement status:approved
Difficulty 5/5 Over a week Newbie friendliness 35/100
egdev6/github-repository-bootstrap#28 ·
Maintainers usually reply within 1 day
All issues in egdev6/github-repository-bootstrap
Similar issues
-
🔧 in development
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
p5.js 2.0+
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
processing/p5.js#9295 · 1 comment ·
Maintainers usually reply within 3 days
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mastra-ai/mastra#27210 · 1 comment ·
Maintainers usually reply within 1 day
-
content html
Difficulty 2/5 1-3 hours Newbie friendliness 82/100