CII-Best-Practices
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
According to the scorecard the last relevant security recommendation ist to add the CII-Best-Practices Badge.
So we should decide if we want to take care of it or not. If we dont want to do it, we can just mark the entry in the recommendations as wont fix.
Maybe @ljharb can lend a hand, as he helped us do this for fastify?
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 reviewing the scorecard's last relevant security recommendation and the project's current CII-Best-Practices status. Done means either adding the badge or marking that recommendation as wont fix after the project decides; the issue names no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100