mirror of
https://github.com/norandom/OpenUltraSAST.git
synced 2026-10-19 21:19:28 +00:00
docs: plain-English pass over the active specs
Ran the humanizer rules over 79 prose files in the active specs (brief, design, requirements, research and narrative docs). Removed em dashes, significance inflation, forced rule-of-three, bold-label list items and filler. Skipped tasks.md checklists and the retired specs (harnessx-*, openrouter-sast-harness, unseen-repo-evaluation). Every number, path, command, hash and identifier was preserved: checked each file against HEAD for drift in numbers, inline code and code fences, zero drift across all 79 files. Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
Marius Ciepluch
co-authored by
Claude Opus 4.8
Claude Opus 4.8
parent
b08f372022
commit
39a1873e5b
@@ -25,8 +25,8 @@ Fix the scorer and labels first (no engine change). Anchor harvest at the declar
|
||||
|
||||
## Scope
|
||||
|
||||
- **In**: scorer fidelity; label schema; harvest anchor and modes; corpus hygiene for sast; three new slices; dataset pointers; provenance fingerprint; per-profile and per-mechanism dashboard; per-profile improve-loop gate; offline tests.
|
||||
- **Out**: any change to taint, facts, CST walker, or dispositions (engine specs); tolerating tree-sitter ERROR nodes (engine); BaxBench generation and exploit-labelled slices (needs deep mode; later); profile-specific fact tables; making any dashboard a merge gate; vendoring SecBench.js test files (no license).
|
||||
- In: scorer fidelity; label schema; harvest anchor and modes; corpus hygiene for sast; three new slices; dataset pointers; provenance fingerprint; per-profile and per-mechanism dashboard; per-profile improve-loop gate; offline tests.
|
||||
- Out: any change to taint, facts, CST walker, or dispositions (engine specs); tolerating tree-sitter ERROR nodes (engine); BaxBench generation and exploit-labelled slices (needs deep mode; later); profile-specific fact tables; making any dashboard a merge gate; vendoring SecBench.js test files (no license).
|
||||
|
||||
## Boundary Candidates
|
||||
|
||||
@@ -42,14 +42,14 @@ Fix the scorer and labels first (no engine change). Anchor harvest at the declar
|
||||
|
||||
## Upstream / Downstream
|
||||
|
||||
- **Upstream**: pair catalog schema; overlay eval path; `build_pair_signals`; `run_improvement` accept gate; preprocess tags.
|
||||
- **Downstream**: `overlay-ir-completeness` and `guard-dominance-regime` measure against these slices and vocabularies; later `baxgen` slice reuses provenance and mechanism fields.
|
||||
- Upstream: pair catalog schema; overlay eval path; `build_pair_signals`; `run_improvement` accept gate; preprocess tags.
|
||||
- Downstream: `overlay-ir-completeness` and `guard-dominance-regime` measure against these slices and vocabularies; later `baxgen` slice reuses provenance and mechanism fields.
|
||||
|
||||
## Existing Spec Touchpoints
|
||||
|
||||
- **Supersedes**: `real-world-vfc-slice` (corpus/scorer plane). Its seed pairs, harvest script, and dual scoreboard are kept and extended.
|
||||
- **Extends**: roadmap direct candidate "record inventory vs overlay Youden side-by-side in sast JSON".
|
||||
- **Adjacent**: `propose-adjudicate-prove` (one additive field on `OverlayRecord`), `harnessx-self-improving-rulesets` (accept gate grows a per-profile clause, ledger format unchanged).
|
||||
- Supersedes: `real-world-vfc-slice` (corpus/scorer plane). Its seed pairs, harvest script, and dual scoreboard are kept and extended.
|
||||
- Extends: roadmap direct candidate "record inventory vs overlay Youden side-by-side in sast JSON".
|
||||
- Adjacent: `propose-adjudicate-prove` (one additive field on `OverlayRecord`), `harnessx-self-improving-rulesets` (accept gate grows a per-profile clause, ledger format unchanged).
|
||||
|
||||
## Constraints
|
||||
|
||||
|
||||
@@ -172,11 +172,11 @@ tests/
|
||||
|
||||
### Modified Files
|
||||
|
||||
- `src/openultrasast/pairs.py` — see above; `OVERLAY_SLICES` grows; `PairCase` gains `provenance`, `mechanism` (on expected), `split`, `known_limit`.
|
||||
- `src/openultrasast/semantic/overlay.py` — fill `function` from the `FunctionIR` whose range contains the record line; default `None`.
|
||||
- `src/openultrasast/improve/evolve.py` — `_Eval` computes `per_profile` on holdout; new reject reason `profile_regression:<profile>`.
|
||||
- `src/openultrasast/preprocess.py`, `reports.py`, `cli.py` — wiring only.
|
||||
- `benchmarks/pairs/README.md`, `.kiro/steering/roadmap.md` — slice list and spec order.
|
||||
- `src/openultrasast/pairs.py`: see above; `OVERLAY_SLICES` grows; `PairCase` gains `provenance`, `mechanism` (on expected), `split`, `known_limit`.
|
||||
- `src/openultrasast/semantic/overlay.py`: fill `function` from the `FunctionIR` whose range contains the record line; default `None`.
|
||||
- `src/openultrasast/improve/evolve.py`: `_Eval` computes `per_profile` on holdout; new reject reason `profile_regression:<profile>`.
|
||||
- `src/openultrasast/preprocess.py`, `reports.py`, `cli.py`: wiring only.
|
||||
- `benchmarks/pairs/README.md`, `.kiro/steering/roadmap.md`: slice list and spec order.
|
||||
|
||||
## System Flows
|
||||
|
||||
|
||||
@@ -8,9 +8,9 @@ Engineers evolving OpenUltraSAST's overlay cannot trust the pair scoreboard: cov
|
||||
|
||||
## Boundary Context
|
||||
|
||||
- **In scope**: pair scorer fidelity; catalog label schema (function, mechanism, provenance, known limits, held-out split); harvest anchoring and extraction modes; sast corpus hygiene; `vibe-py`, `vfc-js`, `agent-vfc` slices; dataset pointers; deterministic provenance fingerprint at scan time; per-profile and per-mechanism dashboard; per-profile acceptance in the improve loop; offline tests.
|
||||
- **Out of scope**: taint, facts, CST walker, dispositions, or tolerance of parser ERROR nodes (engine specs); BaxBench generation slices; profile-specific fact tables or thresholds; any new merge gate; vendoring files without a stated license; LLM-based classification.
|
||||
- **Adjacent expectations**: `local` stays the 100% pair gate; the stage-1 smoke gate stays inventory-only; `OverlayRecord` may gain one optional additive field; the improve loop's existing accept gate (recall floor, FP ceiling, score, no matched regression) stays and grows one clause; ledger file formats do not change.
|
||||
- In scope: pair scorer fidelity; catalog label schema (function, mechanism, provenance, known limits, held-out split); harvest anchoring and extraction modes; sast corpus hygiene; `vibe-py`, `vfc-js`, `agent-vfc` slices; dataset pointers; deterministic provenance fingerprint at scan time; per-profile and per-mechanism dashboard; per-profile acceptance in the improve loop; offline tests.
|
||||
- Out of scope: taint, facts, CST walker, dispositions, or tolerance of parser ERROR nodes (engine specs); BaxBench generation slices; profile-specific fact tables or thresholds; any new merge gate; vendoring files without a stated license; LLM-based classification.
|
||||
- Adjacent expectations: `local` stays the 100% pair gate; the stage-1 smoke gate stays inventory-only; `OverlayRecord` may gain one optional additive field; the improve loop's existing accept gate (recall floor, FP ceiling, score, no matched regression) stays and grows one clause; ledger file formats do not change.
|
||||
|
||||
## Requirements
|
||||
|
||||
@@ -23,7 +23,7 @@ Engineers evolving OpenUltraSAST's overlay cannot trust the pair scoreboard: cov
|
||||
1. When an overlay slice pair is scored, the system shall count a `coverage` record that carries a source-to-sink flow as a detection on the vulnerable side and as a leak on the fixed side, symmetrically with `promote`.
|
||||
2. When an expected row names a function, the system shall match a promotion or coverage record only if the record lies inside that function's line range.
|
||||
3. When an expected row names neither a rule id nor a sink nor a function, the system shall not count a CWE-only match as a detection and shall flag the row as `weak_label` in the payload.
|
||||
4. When any overlay slice is evaluated, the system shall report inventory and overlay metrics side by side for that slice, not only for `vfc`.
|
||||
4. When any overlay slice is evaluated, the system shall report inventory and overlay metrics side by side for that slice as well as for `vfc`.
|
||||
5. When a pair is evaluated, the system shall report how many files on each side were `parse_failed` and how many proposals were `unadjudicated`, so parser loss is visible on the dashboard.
|
||||
6. The system shall keep `local` as the only slice whose result can fail CI.
|
||||
7. Where a hunter model is configured, the system shall report a third scorer, `hunter`, that runs the tool hunter on each isolated pair function and scores it with the same pair rules, so the LLM plane is measured on the same corpus; absence of a model shall skip the scorer with a recorded degradation.
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
|
||||
## Summary
|
||||
|
||||
- **Feature**: `pair-corpus-honesty`
|
||||
- **Discovery Scope**: Extension of the pair catalog, scorer, and harvest; supersedes `real-world-vfc-slice`
|
||||
- **Key Findings**:
|
||||
- Feature: `pair-corpus-honesty`
|
||||
- Discovery Scope: Extension of the pair catalog, scorer, and harvest; supersedes `real-world-vfc-slice`
|
||||
- Key Findings:
|
||||
- The overlay scorer ignores `coverage`. The Java sqli vuln file already produces a coverage record on `prepareCall` from a servlet source; the scorer reports MISS.
|
||||
- The overlay column equals the inventory column on all 176 vfc pairs because C facts have no memory sink, so every proposal is `flow_incomplete` and the scorer falls back to inventory. The dashboard cannot show engine progress until the scorer reports parser and adjudication loss explicitly.
|
||||
- Harvest anchors on the first textual occurrence of the function name. For curl that is the doc comment mention (`Curl_follow()`), so 25 pairs start mid-comment and fail to parse.
|
||||
@@ -18,23 +18,23 @@
|
||||
|
||||
### Scorer blind spots
|
||||
|
||||
- **Context**: Why the sast overlay number did not move after the tree-sitter extra.
|
||||
- **Sources Consulted**: `src/openultrasast/pairs.py` (`_evaluate_overlay_pair`, `_overlay_matches_expected`, `_overlay_leaks`), `semantic/overlay.py`, direct runs of `adjudicate` on the sast files.
|
||||
- **Findings**: only `promote` is counted; `coverage` is excluded on both sides. `_overlay_matches_expected` accepts a CWE-only match. `ExpectedFinding` already has `function` and `line`, and `benchmark._matches_expected` honors them, but the overlay path does not. `OverlayRecord` has no function field; `FunctionIR` has line ranges.
|
||||
- **Implications**: count coverage symmetrically; add optional `function` to `OverlayRecord`; require function or sink or rule id for a match when present; flag CWE-only rows.
|
||||
- Context: Why the sast overlay number did not move after the tree-sitter extra.
|
||||
- Sources Consulted: `src/openultrasast/pairs.py` (`_evaluate_overlay_pair`, `_overlay_matches_expected`, `_overlay_leaks`), `semantic/overlay.py`, direct runs of `adjudicate` on the sast files.
|
||||
- Findings: only `promote` is counted; `coverage` is excluded on both sides. `_overlay_matches_expected` accepts a CWE-only match. `ExpectedFinding` already has `function` and `line`, and `benchmark._matches_expected` honors them, but the overlay path does not. `OverlayRecord` has no function field; `FunctionIR` has line ranges.
|
||||
- Implications: count coverage symmetrically; add optional `function` to `OverlayRecord`; require function or sink or rule id for a match when present; flag CWE-only rows.
|
||||
|
||||
### Harvest anchor defect
|
||||
|
||||
- **Context**: 50 vfc files `parse_failed`.
|
||||
- **Sources Consulted**: `benchmarks/pairs/vfc/harvest.py` `extract_function`; tree-sitter ERROR nodes on `curl-cve-2022-27774/vuln.c` and `curl-cve-2023-38545-do_socks5/vuln.c`.
|
||||
- **Findings**: the name search accepts a match followed by `(` even inside a comment, and the brace search then finds the real body. A second, smaller class is `#if`-split `else if` chains, which tree-sitter cannot attach; that is an engine tolerance question, not harvest.
|
||||
- **Implications**: skip comment and string regions before searching; anchor on a line that starts a declarator; add line-range and hunk modes so Python and JS/TS are covered; report parse loss on the dashboard so the engine spec can measure its tolerance work.
|
||||
- Context: 50 vfc files `parse_failed`.
|
||||
- Sources Consulted: `benchmarks/pairs/vfc/harvest.py` `extract_function`; tree-sitter ERROR nodes on `curl-cve-2022-27774/vuln.c` and `curl-cve-2023-38545-do_socks5/vuln.c`.
|
||||
- Findings: the name search accepts a match followed by `(` even inside a comment, and the brace search then finds the real body. A second, smaller class is `#if`-split `else if` chains, which tree-sitter cannot attach; that is an engine tolerance question, not harvest.
|
||||
- Implications: skip comment and string regions before searching; anchor on a line that starts a declarator; add line-range and hunk modes so Python and JS/TS are covered; report parse loss on the dashboard so the engine spec can measure its tolerance work.
|
||||
|
||||
### Candidate corpora
|
||||
|
||||
- **Context**: User asked for vibe-coded and Node/TypeScript/Python web corpora.
|
||||
- **Sources Consulted**: Real-Vuln-Benchmark repo and paper; SecBench.js repo and ICSE 2023 paper; AIDev dataset card and paper; BaxBench site, repo, and paper; SecurityEval, CodeSecEval, CWEval; CyberSecEval benchmarks README; VibeApps paper; TS-VulBench page; SecureVibeBench repo; GitHub commit search via `gh api search/commits`.
|
||||
- **Findings**:
|
||||
- Context: User asked for vibe-coded and Node/TypeScript/Python web corpora.
|
||||
- Sources Consulted: Real-Vuln-Benchmark repo and paper; SecBench.js repo and ICSE 2023 paper; AIDev dataset card and paper; BaxBench site, repo, and paper; SecurityEval, CodeSecEval, CWEval; CyberSecEval benchmarks README; VibeApps paper; TS-VulBench page; SecureVibeBench repo; GitHub commit search via `gh api search/commits`.
|
||||
- Findings:
|
||||
| Corpus | Languages | Labels | Fixed twin | License | Verdict |
|
||||
|---|---|---|---|---|---|
|
||||
| Real-Vuln-Benchmark | Python web | file, line range, function, CWEs, authorship, FP traps | traps | Apache-2.0 | `vibe-py` |
|
||||
@@ -46,14 +46,14 @@
|
||||
| VibeApps/VibeVulns | TS, JS, React | not released | no | n/a | method only |
|
||||
| TS-VulBench | TS synthetic | paywalled | no | unknown | skip |
|
||||
| SecureVibeBench | C/C++ | agent tasks | n/a | MIT | skip for web |
|
||||
- **Implications**: three slices now; BaxBench after deep mode is stable; CyberSecEval never as recall ground truth.
|
||||
- Implications: three slices now; BaxBench after deep mode is stable; CyberSecEval never as recall ground truth.
|
||||
|
||||
### Classification and branching
|
||||
|
||||
- **Context**: User expects tuning to split into branches per corpus class.
|
||||
- **Sources Consulted**: `improve/evolve.py` accept gate; `ruleset/store.py` ledger; `calibration.py` scope; `preprocess.detect_tags`; `build_pair_signals`.
|
||||
- **Findings**: the accept gate already ANDs four clauses and reverts byte-for-byte. Pair signals carry pair name but no profile. Ledger is one file per target. Preprocess tags are deterministic and per file.
|
||||
- **Implications**: classify on two axes (provenance for gating, mechanism for reporting). Branch the acceptance decision, not the ledger format: reject a change if any profile's holdout regresses. Profile-specific facts and thresholds are deferred to the engine specs where those data live.
|
||||
- Context: User expects tuning to split into branches per corpus class.
|
||||
- Sources Consulted: `improve/evolve.py` accept gate; `ruleset/store.py` ledger; `calibration.py` scope; `preprocess.detect_tags`; `build_pair_signals`.
|
||||
- Findings: the accept gate already ANDs four clauses and reverts byte-for-byte. Pair signals carry pair name but no profile. Ledger is one file per target. Preprocess tags are deterministic and per file.
|
||||
- Implications: classify on two axes (provenance for gating, mechanism for reporting). Branch the acceptance decision, not the ledger format: reject a change if any profile's holdout regresses. Profile-specific facts and thresholds are deferred to the engine specs where those data live.
|
||||
|
||||
## Architecture Pattern Evaluation
|
||||
|
||||
@@ -68,48 +68,48 @@
|
||||
|
||||
### Decision: Count coverage-with-flow as detection and as leak
|
||||
|
||||
- **Context**: Sink aliases will always land as coverage.
|
||||
- **Alternatives Considered**: promote coverage to `promote` in the engine; count coverage only on the vulnerable side.
|
||||
- **Selected Approach**: scorer treats `coverage` with a non-empty source the same as `promote` on both sides.
|
||||
- **Rationale**: `propose-adjudicate-prove` already states coverage enters the same state machine. Asymmetry would inflate recall.
|
||||
- **Trade-offs**: some pairs move from MISS to LEAK; that is the honest reading.
|
||||
- Context: Sink aliases will always land as coverage.
|
||||
- Alternatives Considered: promote coverage to `promote` in the engine; count coverage only on the vulnerable side.
|
||||
- Selected Approach: scorer treats `coverage` with a non-empty source the same as `promote` on both sides.
|
||||
- Rationale: `propose-adjudicate-prove` already states coverage enters the same state machine. Asymmetry would inflate recall.
|
||||
- Trade-offs: some pairs move from MISS to LEAK; that is the honest reading.
|
||||
|
||||
### Decision: Function-scoped matching with weak-label flagging
|
||||
|
||||
- **Context**: CWE-only matching over-counts.
|
||||
- **Selected Approach**: expected rows carry `function`; match requires the record inside that function's lines; rows with no function, sink, or rule id are `weak_label` and never match by CWE alone.
|
||||
- **Trade-offs**: vfc recall may drop on first run; the drop is real.
|
||||
- Context: CWE-only matching over-counts.
|
||||
- Selected Approach: expected rows carry `function`; match requires the record inside that function's lines; rows with no function, sink, or rule id are `weak_label` and never match by CWE alone.
|
||||
- Trade-offs: vfc recall may drop on first run; the drop is real.
|
||||
|
||||
### Decision: Provenance is deterministic and closed
|
||||
|
||||
- **Context**: No LLM in classification.
|
||||
- **Selected Approach**: signals from `.claude/`, `CLAUDE.md`, `AGENTS.md`, `.cursor/`, `.github/copilot-instructions.md`, Lovable meta tag, "Generated with Claude Code", and co-author trailers for Claude, Codex, Copilot, Cursor, Devin, Jules when a git log is readable. Threshold for `agent` on a git tree: at least 85% of commits or lines in the last N commits carry a signal, following the VibeApps method; otherwise `mixed` when any signal exists; `human` when none; `synthetic` only from catalog declaration.
|
||||
- **Trade-offs**: repos that scrub trailers read as human. Acceptable; the label is a profile, not a verdict.
|
||||
- Context: No LLM in classification.
|
||||
- Selected Approach: signals from `.claude/`, `CLAUDE.md`, `AGENTS.md`, `.cursor/`, `.github/copilot-instructions.md`, Lovable meta tag, "Generated with Claude Code", and co-author trailers for Claude, Codex, Copilot, Cursor, Devin, Jules when a git log is readable. Threshold for `agent` on a git tree: at least 85% of commits or lines in the last N commits carry a signal, following the VibeApps method; otherwise `mixed` when any signal exists; `human` when none; `synthetic` only from catalog declaration.
|
||||
- Trade-offs: repos that scrub trailers read as human. Acceptable; the label is a profile, not a verdict.
|
||||
|
||||
### Decision: Branch the accept decision, not the data
|
||||
|
||||
- **Context**: Overfitting risk with per-slice tuning.
|
||||
- **Selected Approach**: `run_improvement` evaluates holdout pairs per profile; any profile regression beyond tolerance rejects. Profiles capped at four. Minimum holdout size reported.
|
||||
- **Follow-up**: profile-keyed facts land with the engine specs, gated by this clause.
|
||||
- Context: Overfitting risk with per-slice tuning.
|
||||
- Selected Approach: `run_improvement` evaluates holdout pairs per profile; any profile regression beyond tolerance rejects. Profiles capped at four. Minimum holdout size reported.
|
||||
- Follow-up: profile-keyed facts land with the engine specs, gated by this clause.
|
||||
|
||||
## Risks & Mitigations
|
||||
|
||||
- Recall numbers drop after function-scoped matching and weak-label flags — expected; record before and after in the roadmap.
|
||||
- SecBench.js has no license — never vendor its files; harvest from upstream package repos and record each package license.
|
||||
- Agent-authored commits may be false labels (a "fix" that was not a vuln) — human review required; keep `agent-vfc` small.
|
||||
- Real-Vuln-Benchmark apps are educational and CTF style — say so in the slice README; do not treat `vibe-py` as production.
|
||||
- Held-out halves are small on day one — report minimum-size warnings; do not gate on a profile under the minimum.
|
||||
- Recall numbers drop after function-scoped matching and weak-label flags; expected; record before and after in the roadmap.
|
||||
- SecBench.js has no license; never vendor its files; harvest from upstream package repos and record each package license.
|
||||
- Agent-authored commits may be false labels (a "fix" that was not a vuln); human review required; keep `agent-vfc` small.
|
||||
- Real-Vuln-Benchmark apps are educational and CTF style; say so in the slice README; do not treat `vibe-py` as production.
|
||||
- Held-out halves are small on day one; report minimum-size warnings; do not gate on a profile under the minimum.
|
||||
|
||||
## References
|
||||
|
||||
- [Real-Vuln-Benchmark](https://github.com/kolega-ai/Real-Vuln-Benchmark) — Apache-2.0, manifest with pinned SHAs, ground-truth schema
|
||||
- [RealVuln paper](https://arxiv.org/abs/2604.13764) — 26 human plus 40 LLM-generated Python repos, FP traps
|
||||
- [SecBench.js](https://github.com/cristianstaicu/SecBench.js) — 600 npm vulns, `fixCommit`, `sinkLocation`
|
||||
- [Real-Vuln-Benchmark](https://github.com/kolega-ai/Real-Vuln-Benchmark): Apache-2.0, manifest with pinned SHAs, ground-truth schema
|
||||
- [RealVuln paper](https://arxiv.org/abs/2604.13764): 26 human plus 40 LLM-generated Python repos, FP traps
|
||||
- [SecBench.js](https://github.com/cristianstaicu/SecBench.js): 600 npm vulns, `fixCommit`, `sinkLocation`
|
||||
- [SecBench.js paper](https://software-lab.org/publications/icse2023_SecBenchJS.pdf)
|
||||
- [AIDev dataset](https://huggingface.co/datasets/hao-li/AIDev) — agent-authored PRs, CC-BY-4.0 index
|
||||
- [BaxBench](https://github.com/logic-star-ai/baxbench) — MIT, scenarios and exploits, generation by CLI
|
||||
- [AIDev dataset](https://huggingface.co/datasets/hao-li/AIDev): agent-authored PRs, CC-BY-4.0 index
|
||||
- [BaxBench](https://github.com/logic-star-ai/baxbench): MIT, scenarios and exploits, generation by CLI
|
||||
- [SecurityEval](https://github.com/s2e-lab/SecurityEval), [CodeSecEval](https://arxiv.org/pdf/2407.02395), [CWEval](https://github.com/Co1lin/CWEval)
|
||||
- [CyberSecEval](https://github.com/meta-llama/PurpleLlama/tree/main/CybersecurityBenchmarks) — labels defined by ICD rules
|
||||
- [VibeApps paper](https://arxiv.org/html/2606.23130v1) — identification method
|
||||
- `.kiro/specs/real-world-vfc-slice/` — superseded corpus spec
|
||||
- Memory note `overlay-gaps-diagnosis-2026-09` — measured state and engine gaps
|
||||
- [CyberSecEval](https://github.com/meta-llama/PurpleLlama/tree/main/CybersecurityBenchmarks): labels defined by ICD rules
|
||||
- [VibeApps paper](https://arxiv.org/html/2606.23130v1): identification method
|
||||
- `.kiro/specs/real-world-vfc-slice/`: superseded corpus spec
|
||||
- Memory note `overlay-gaps-diagnosis-2026-09`: measured state and engine gaps
|
||||
|
||||
Reference in New Issue
Block a user