POST: matching vulnerabilities to packages is not easy

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale

Research direction

Start by reading the linked discussion and the initial publication, then compare the upstream and downstream advisory links listed in the issue. The post is done when it clearly explains why matching vulnerabilities to packages is difficult and reflects the cited evidence without leaving the affected or fixed versions ambiguous.

Written by the indexing model from the issue text.

Description

blog

This would be a post to explain the issues in https://github.com/aboutcode-org/dejacode/discussions/302#discussioncomment-12995054

Links:

Why does this matter? The upstream report was clear on affected and fixed version. Downstream advisories make the issue less clear and a source of possible confusion.

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.