Skip to content

fix: invert risk_score semantics (higher = riskier)#1

Merged
msoffredi merged 6 commits into
mainfrom
risk-score-inversion
Jul 1, 2026
Merged

fix: invert risk_score semantics (higher = riskier)#1
msoffredi merged 6 commits into
mainfrom
risk-score-inversion

Conversation

@msoffredi

Copy link
Copy Markdown
Contributor

Summary

  • risk_score from the packagerating.com API is being inverted upstream so higher now means riskier (previously higher meant safer — confusing for a field called "Risk").
  • Flips fail-on-risk gating to fail when risk_score is above the threshold (was: below). fail-on-general/fail-on-automation unchanged.
  • Flips the Risk column's ✅/⚠️ report-table badge direction to match.
  • Updates action.yml and README.md (gating example + a separate, correctly-inverted Risk score-ranges table).
  • Bumps version to 1.1.0.

Test plan

  • 38/38 tests passing (npm test)
  • Typecheck clean (npm run typecheck)
  • Build verified (npm run build)
  • Reviewed clean by final whole-branch review — no Critical/Important issues

🤖 Generated with Claude Code

msoffredi and others added 6 commits July 1, 2026 10:49
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>
@msoffredi
msoffredi merged commit 71d658c into main Jul 1, 2026
1 check passed
@msoffredi
msoffredi deleted the risk-score-inversion branch July 2, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant