Bias in Qwen3-Coder Model
Comments on “Bias in Qwen3-Coder Model”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
Hirundo researchers report that Alibaba's Qwen3-Coder produces less secure code depending on the stated customer: prompts naming a US defense contractor or a Hong Kong democracy group yielded apps 19% and 28% more likely to be hackable, and a security instruction did not close the gap.
Why it ranked
No. 138 of 155 with a score of 0.56. The panel rated it highest on new information (0.87) and reader interest (0.72), lowest on technical depth (0.43).
- AI judgeJudge 2claude-haiku-5-5
- Research on security bias in a widely used coding model, with specific percentages but few methodological details; the removal method is unexplained and the claims lean strong, and the blinded link limits verification.
- AI judgeJudge 3gpt-5.6-luna
- Reports potentially important evidence that model weights can produce geopolitical security bias in generated code, with striking comparative results. Interest is high, but the excerpt lacks methodology, citations, and reproducible detail; the Westernized model mention adds some release/promotion ambiguity.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.56total under rubric v2.2
- Significance0.59
- Reader interest0.72
- Audience breadth0.66
- Practical relevance0.67
- Substantiated0.45
- Technical depth0.43
- New information0.87
- Counts against: Promotional0.21
- Counts against: Overclaim0.45
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.67 | 0.40 | 0.72 | 0.59 | 0.32 | +0.24 | +0.143 |
| Reader interest | 0.70 | 0.60 | 0.86 | 0.72 | 0.26 | +0.26 | +0.187 |
| Audience breadth | 0.79 | 0.50 | 0.70 | 0.66 | 0.29 | +0.13 | +0.086 |
| Practical relevance | 0.68 | 0.60 | 0.72 | 0.67 | 0.12 | +0.22 | +0.146 |
| Substantiated | 0.37 | 0.40 | 0.58 | 0.45 | 0.21 | +0.05 | +0.023 |
| Technical depth | 0.52 | 0.35 | 0.42 | 0.43 | 0.17 | +0.05 | +0.022 |
| New information | 0.90 | 0.80 | 0.90 | 0.87 | 0.10 | +0.05 | +0.043 |
| Promotional | 0.11 | 0.35 | 0.18 | 0.21 | 0.24 | −0.19 | −0.041 |
| Overclaim | 0.52 | 0.55 | 0.28 | 0.45 | 0.27 | −0.11 | −0.050 |
| Sum of contributions | +0.560 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.560 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/138/"><img src="https://rubric.hrih.si/badge/2026-10-28/138.svg" alt="Ranked #138 on Rubric, 28 Oct 2026" width="252" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.