Populate Security-Severity Value
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 131
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
GitHub Code Scanning Recognizes a security-severity value to specify a CWE value for a finding. DevSkim doesn't have these values defined, but it might be nice to have that included in the rules. This would also require a small amount of work to then inject those values into the output sarif.
Follow up from #605, #606
Describe the solution you'd like
Each rule would need to be evaluated to determine the appropriate CWE level on a float scale from 0-10.
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
Review the existing rule definitions and SARIF output generation, then compare the requested security-severity field with GitHub's SARIF reportingDescriptor documentation. Determine appropriate CWE severity values for each rule and verify that generated SARIF output includes them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100