fix: invert risk_score semantics (higher = riskier)#1
Merged
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Matches the inverted risk_score semantics (higher = riskier) shipped upstream. fail-on-general and fail-on-automation are unchanged. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Risk now shows ✅ at or below the threshold and⚠️ above it, opposite of General/Automation, matching the new higher-means-riskier semantics. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.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.
Summary
risk_scorefrom the packagerating.com API is being inverted upstream so higher now means riskier (previously higher meant safer — confusing for a field called "Risk").fail-on-riskgating to fail whenrisk_scoreis above the threshold (was: below).fail-on-general/fail-on-automationunchanged.action.ymlandREADME.md(gating example + a separate, correctly-inverted Risk score-ranges table).Test plan
npm test)npm run typecheck)npm run build)🤖 Generated with Claude Code