RUSTSEC ingestion request: ignore advisories with `informational` field
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Locate the ingestion job that converts RUSTSEC advisories into GHSAs, then inspect how advisory metadata is parsed and filtered. Use the linked RustSec example as the input case; done means advisories containing an informational field are not republished as GHSAs.
Written by the indexing model from the issue text.
Description
Somewhere there is a job that ingests advisories from https://github.com/rustsec/advisory-db and republishes them here as GHSAs.
Speaking on behalf of @RustSec, our database contains a mixture of advisories for security vulnerabilities and advisories for other defects which are not immediately security critical, like unsoundness or unmaintained packages (I now regret not more cleanly isolating these advisories).
Here is a recent example: https://github.com/rust-random/rand/issues/1774
These advisories contain an informational field in their metadata, e.g.:
https://github.com/rustsec/advisory-db/blob/cf79a10/crates/rand/RUSTSEC-2026-0097.md?plain=1#L7
This is a request to change the ingestion job which converts RUSTSEC advisories into GHSAs to ignore any advisories containing the informational field as these advisories do not represent specific vulnerabilities.
See also: https://github.com/rustsec/advisory-db/issues/2572
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 772
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 46
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.
More from github/advisory-database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#9255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#9164 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8994 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#8898 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8841 ·
All issues in github/advisory-database
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Business User Story
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[Documentation Request] vLLM kv_load_failure_policy doesn't apply to load failures in L2 adapters Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100