Tar-minefield shows where tar implementations disagree
Comments on “Tar-minefield shows where tar implementations disagree”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
tar-minefield is a Hacker News project that catalogs ambiguities in the tar archive format where implementations extract the same file differently, creating security risks when scanners and extractors disagree.
Why it ranked
No. 36 of 155 with a score of 0.64. The panel rated it highest on new information (0.94) and substantiated (0.90), lowest on audience breadth (0.55).
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-substantiated technical test suite and dataset on tar parsing ambiguities with security implications; a working draft of a specification, niche but relevant to builders and security-minded engineers, with little overlap with recent stories.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed, data-backed test suite exposes security-relevant disagreement among tar implementations and proposes a measurable compatibility policy. It is highly actionable for archive, package-management, and security-tool authors, though narrower than a field-wide development.
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.64total under rubric v2.2
- Significance0.55
- Reader interest0.69
- Audience breadth0.55
- Practical relevance0.69
- Substantiated0.90
- Technical depth0.87
- New information0.94
- Counts against: Promotional0.06
- Counts against: Overclaim0.15
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.64 | 0.40 | 0.62 | 0.55 | 0.24 | +0.24 | +0.133 |
| Reader interest | 0.62 | 0.60 | 0.84 | 0.69 | 0.24 | +0.26 | +0.179 |
| Audience breadth | 0.70 | 0.40 | 0.55 | 0.55 | 0.30 | +0.13 | +0.072 |
| Practical relevance | 0.73 | 0.60 | 0.72 | 0.69 | 0.14 | +0.22 | +0.151 |
| Substantiated | 0.96 | 0.80 | 0.93 | 0.90 | 0.16 | +0.05 | +0.045 |
| Technical depth | 0.91 | 0.85 | 0.86 | 0.87 | 0.06 | +0.05 | +0.044 |
| New information | 0.93 | 0.90 | 0.98 | 0.94 | 0.08 | +0.05 | +0.047 |
| Promotional | 0.05 | 0.10 | 0.04 | 0.06 | 0.06 | −0.19 | −0.012 |
| Overclaim | 0.22 | 0.20 | 0.03 | 0.15 | 0.19 | −0.11 | −0.017 |
| Sum of contributions | +0.640 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.640 | ||||||
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/36/"><img src="https://rubric.hrih.si/badge/2026-10-28/36.svg" alt="Ranked #36 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
Elsewhere
Elsewhere: HN 4 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.