Skip to content

fix(certify): reweight when code is unscorable instead of auto-failing#61

Merged
hummbl-dev merged 1 commit intomainfrom
fix/claude/certify-reweight
Apr 19, 2026
Merged

fix(certify): reweight when code is unscorable instead of auto-failing#61
hummbl-dev merged 1 commit intomainfrom
fix/claude/certify-reweight

Conversation

@hummbl-dev
Copy link
Copy Markdown
Owner

Summary

Repos with no Python LOC were getting code_score=0 → automatic FAILED certification.
Now reweights to governance 60% + deps 40% when code is unscorable.

Before: prometheus, traefik, gh CLI → FAILED (47.0)
After: prometheus, traefik, gh CLI → CERTIFIED (94.0)

Adds transparent note: "Code quality not scored (no supported analyzers for primary language)"

Found by scanning 10 Go repos — all failed despite excellent governance.

Test plan

  • Non-scorable code reweights correctly
  • Reason notes "not scored"
  • Scorable repos unaffected

🤖 Generated with Claude Code

Previously, repos with no Python LOC got code_score=0, causing
automatic FAILED certification even for well-governed Go/Rust/TS
repos. Now reweights to governance 60% + deps 40% when code scoring
is unavailable, with a transparent note in reasons.

Before: prometheus/prometheus → FAILED (47.0)
After:  prometheus/prometheus → CERTIFIED (94.0)

Found by scanning 10 Go repos: all failed despite excellent
governance because code scoring was Python-only.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@hummbl-dev hummbl-dev force-pushed the fix/claude/certify-reweight branch from f2ca4a6 to e9b6da0 Compare April 19, 2026 05:26
@hummbl-dev hummbl-dev merged commit 5148304 into main Apr 19, 2026
2 of 3 checks passed
@hummbl-dev hummbl-dev deleted the fix/claude/certify-reweight branch April 19, 2026 05:27
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