fix: centralize severity ordering#61
Open
zerone0x wants to merge 1 commit into
Open
Conversation
|
@zerone0x is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
blackyking13
approved these changes
May 10, 2026
zerone0x
force-pushed
the
fix/canonical-severity-order
branch
from
221a3c3 to
eaaa142
Compare
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
2 participants
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.
Summary
SEVERITY_ORDERexport from@deepsec/coreLOWin sandbox severity ranking so--min-severityfilters handle LOW consistentlyFixes #48.
Test plan
pnpm -r buildpnpm lintpnpm test:unit