Add criterion for CLI, filesystem, etc I/O
Open
Nobody has claimed this yet.
criteria
enhancement
help wanted
- Dominant language
- Go
- Stars
- 166
- Forks
- 44
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
Not sure I agree with this one... Inclined to think that other inputs and outputs need documentation as well— such as CLI input and output or filesystem i/o.
Originally posted by @eddie-knight in https://github.com/ossf/security-baseline/issues/154#issuecomment-2602795138
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
The issue provides no repository files, tests, or entry points to follow. Start by reviewing the discussion in issue 154 and the repository's existing security criteria, focusing on the proposed CLI and filesystem I/O coverage. Done requires an agreed scope and a documented criterion for the relevant input and output types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100