feat: CVE conversion triager tool#4916
Merged
Merged
Conversation
This change introduces a new triage page to visualize and compare CVE conversion data across different stages and environments. - Added `gcp/website/triage_handlers.py` to handle triage requests and proxy GCS file access. - Registered the new blueprint in `gcp/website/main.py`. - Created the frontend template `gcp/website/frontend3/src/templates/triage.html` with a 3-column layout. - Implemented frontend logic in `gcp/website/frontend3/src/triage.js` to fetch and display JSON data from GCS or the API. - Added styles in `gcp/website/frontend3/src/triage.scss`. - Updated Webpack configuration to include the new triage entry point. - Verified with unit tests and frontend screenshots. Co-authored-by: jess-lowe <86962800+jess-lowe@users.noreply.github.com>
This change introduces a new triage page to visualize and compare CVE conversion data across different stages and environments. - Added `gcp/website/triage_handlers.py` to handle triage requests and proxy GCS file access. - Registered the new blueprint in `gcp/website/main.py`. - Created the frontend template `gcp/website/frontend3/src/templates/triage.html` with a 3-column layout. - Implemented frontend logic in `gcp/website/frontend3/src/triage.js` to fetch and display JSON data from GCS or the API. - Added styles in `gcp/website/frontend3/src/triage.scss`. - Updated Webpack configuration to include the new triage entry point. - Verified with unit tests and frontend screenshots. Co-authored-by: jess-lowe <86962800+jess-lowe@users.noreply.github.com>
This change introduces a new triage page to visualize and compare CVE conversion data across different stages and environments. - Added `gcp/website/triage_handlers.py` to handle triage requests and proxy GCS file access. - Registered the new blueprint in `gcp/website/main.py`. - Created the frontend template `gcp/website/frontend3/src/templates/triage.html` with a 3-column layout. - Implemented frontend logic in `gcp/website/frontend3/src/triage.js` to fetch and display JSON data from GCS or the API. - Added styles in `gcp/website/frontend3/src/triage.scss`. - Updated Webpack configuration to include the new triage entry point. - Verified with unit tests and frontend screenshots. Co-authored-by: jess-lowe <86962800+jess-lowe@users.noreply.github.com>
This change introduces a new triage page to visualize and compare CVE conversion data across different stages and environments. - Added `gcp/website/triage_handlers.py` to handle triage requests and proxy GCS file access. - Registered the new blueprint in `gcp/website/main.py`. - Created the frontend template `gcp/website/frontend3/src/templates/triage.html` with a 3-column layout. - Implemented frontend logic in `gcp/website/frontend3/src/triage.js` to fetch and display JSON data from GCS or the API. - Added styles in `gcp/website/frontend3/src/triage.scss`. - Updated Webpack configuration to include the new triage entry point. - Verified with unit tests and frontend screenshots. Co-authored-by: jess-lowe <86962800+jess-lowe@users.noreply.github.com>
…44985313989 feat: Add CVE conversion triage page
…44985313989 fix: improve patching issues with triage tool
jess-lowe
commented
Feb 26, 2026
Contributor
Author
|
/gemini review |
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a new CVE conversion triager tool, which is a great addition for comparing different CVE record versions. The implementation includes a new frontend page with its corresponding JavaScript and SCSS, and a backend proxy handler in Python. The overall structure is well-thought-out. I've included several suggestions to enhance code quality, maintainability, and adherence to best practices in both the frontend and backend code.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
another-rex
previously approved these changes
Feb 27, 2026
jess-lowe
commented
Mar 2, 2026
another-rex
approved these changes
Mar 4, 2026
tymzd
pushed a commit
to tymzd/osv.dev
that referenced
this pull request
Apr 13, 2026
Quite often do we need to compare multiple records of one CVE record to triage conversion issues, so this tool will allow us to compare three versions at a time. <img width="2557" height="1185" alt="image" src="https://github.com/user-attachments/assets/beb213fd-a2a0-4fe0-895d-1454bccc722b" /> You can select from the following record locations: - the og cve5 record - the og NVD record - the nvd-converted osv record in prod - the nvd-conversion metrics notes in prod - the nvd-converted osv record in test - the nvd-conversion metrics notes in test - the cve5-converted osv record in prod - the cve5-conversion metrics notes in prod - the cve5-converted osv record in test - the cve5-conversion metrics notes in test - the combined output in prod - the combined output in test - prod api - test api It currently exists at /triage, and utilises a proxy mechanism to load the records, but not as a path (as to prevent accessing unrelated parts of the bucket) In the future could add a tool for an LLM to help triage what the actual problem is, but that's for another day --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Quite often do we need to compare multiple records of one CVE record to triage conversion issues, so this tool will allow us to compare three versions at a time.

You can select from the following record locations:
It currently exists at /triage, and utilises a proxy mechanism to load the records, but not as a path (as to prevent accessing unrelated parts of the bucket)
In the future could add a tool for an LLM to help triage what the actual problem is, but that's for another day