trailofbits / trailofbits/vscode-weaudit
Feature request: Add a mark on all files in-scope if a scope file is available in the project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 35
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 8
Description
Hi,
I was thinking about a feature which could be really helpful during audit contests:
Add a way to specify a scope file and an option to put a mark on all in-scope files on the vscode file tree.
It would avoid a lot of back and forth when reporting issues in big project since you would already know which files are in-scope in VScode.
Moreover some scope files are not that easy to read/search in, or not as easy as a little (blue?) mark on the vscode file tree.
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name files, tests, or an existing scope-file format. Start by clarifying which scope files and VS Code tree marks are supported, how in-scope files are identified, and what happens when no scope file is available. Done means the agreed scope is visibly marked in the file tree and the behavior is covered by suitable tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100