openai / openai/codex-security
Show scan scope, budget semantics, and expected output before paid work begins
Open
Nobody has claimed this yet.
area:cli
area:cost
documentation
enhancement
priority:p2
- Dominant language
- TypeScript
- Stars
- 10.8k
- Forks
- 801
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 257
Description
I set a $20 budget. It spent the whole $20 budget getting setup. How can I budget something when I have no ability to estimate it's expected cost? Am I supposed to set it to $50 now and just hope I don't burn a $50 budget on top of a $20 budget? How do I estimate before I run? :(
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
No files or tests are named. Start at the CLI scan entry point and trace setup, budget handling, and the output shown before paid work begins. Review existing scan behavior and document the expected scope, budget semantics, and pre-work estimate so users can understand costs before execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100