openai / openai/codex-security
Surface multiscan run warnings in campaign summaries
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.8k
- Forks
- 801
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 257
Description
Issue #248 also calls for run warnings to be reflected in the multiscan campaign summary, similar to failures.\n\nPR #810 persists run warnings in results.jsonl and replays them on resume, but intentionally leaves campaign summary accounting unchanged. A repository can therefore complete with persisted operational warnings while the top-level summary still counts it as an ordinary completed scan.\n\nFollow-up scope:\n- decide how operational run warnings should appear in MultiscanResult / CLI campaign summary without conflating them with incomplete coverage;\n- preserve existing completed status semantics for successful scans;\n- add summary-level regression coverage for warned-but-complete repositories and resumed receipts.
Contributor guide
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.
Research direction
Start by tracing the MultiscanResult and CLI campaign-summary paths, then inspect how results.jsonl warnings and resumed receipts from PR #810 are represented. Add summary-level regression coverage for warned-but-complete repositories and resumed receipts; done means warnings appear without changing successful completed status semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100