Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Parse/store severity levels from GitHub vulnerability alerts #33993

Open
rarkins opened this issue Feb 2, 2025 · 0 comments
Open

Parse/store severity levels from GitHub vulnerability alerts #33993

rarkins opened this issue Feb 2, 2025 · 0 comments
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people

Comments

@rarkins
Copy link
Collaborator

rarkins commented Feb 2, 2025

Describe the proposed change(s).

GitHub's REST API returns a severity field. We should record this along with the vulnerability details, and also ideally computer the highest severity per-branch.

A good time to convert to using zod in this API response too.
@rarkins rarkins added the priority-4-low Low priority, unlikely to be done unless it becomes important to more people label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rarkins