Requirement: Secure development knowledge
Open
Nobody has claimed this yet.
CII-best-practices
discussion
never-stale
- Dominant language
- Go
- Stars
- 548
- Forks
- 133
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Original discussion: https://github.com/nodejs/security-wg/pull/954/files#r1179649274
@mhdawson @tniessen
The project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.)
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 with the original discussion linked in the issue, including the referenced “details” section, to determine the exact requirements and expected evidence. Done means the project’s compliance with the secure-development-knowledge requirement is clearly established and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100