Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Change history for GHSA

Open
#6,632 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
security

Research direction

Start by reviewing how GHSA information and affected packages are currently updated and exposed, then compare the requested history with the NVD feature. Define which changes and dates the history should show and how users would access it; done means the scope and presentation of a useful GHSA change history are agreed.

Written by the indexing model from the issue text.

Description

I would be very grateful if there were a change history for the GHSA. The information and affected packages change over time, so it is sometimes very difficult to understand in CVE management systems why a CVE has been visible or not anymore projects since a specific date. The NVD DB has this feature, and it is very helpful.

Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 15h
Merged PRs (30d)
46

Contributor guide

Open the contributing guide

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 github/advisory-database

All issues in github/advisory-database

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.