POST: it is hard to rate the severity of vulnerabiliies

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
huggingface
Domain
content

Research direction

Start by reviewing the linked VLAI model, NIST metric, and vulnerablecode discussion to define the post's scope. Determine whether the contribution is a researched comparison of severity metrics or an implementation; the issue names no repository file, test, format, or acceptance criteria.

Written by the indexing model from the issue text.

Description

blog

It is hard to rate the severity of vulnerabilities!

Let's look beyond the alphabet soup of CVSS, KEY, EPSS, SSVC.

See also Tod Beardsley https://www.youtube.com/watch?v=348LcypOPI0

Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.