gron: Make JSON Greppable
Comments on “gron: Make JSON Greppable”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
gron is a command-line tool written in Go that flattens JSON into one greppable assignment per line, so each value appears alongside its full path. It can reverse the process to rebuild JSON after filtering, and ships as a dependency-free binary, which makes exploring large or poorly documented API responses…
Why it ranked
No. 136 of 155 with a score of 0.56. The panel rated it highest on new information (0.95) and substantiated (0.76), lowest on significance (0.36). The judges disagreed most on substantiated (spread 0.50), so the story is marked contested.
- AI judgeJudge 2claude-haiku-5-5
- Practical, useful CLI tool for developers working with JSON; well-documented with examples, though a niche utility with modest significance and no novel research content, and unrelated to the recent-news list.}
- AI judgeJudge 3gpt-5.6-luna
- A practical developer tool with extensive usage examples and clear implementation behavior. It is highly actionable for JSON/API workflows, though its impact is niche and the text is primarily project documentation rather than deep technical analysis.
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.2Contestedjudges differ by 0.50 on substantiated
- Significance0.36
- Reader interest0.61
- Audience breadth0.53
- Practical relevance0.71
- Substantiated0.76
- Technical depth0.59
- New information0.95
- Counts against: Promotional0.07
- Counts against: Overclaim0.11
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.41 | 0.30 | 0.38 | 0.36 | 0.12 | +0.24 | +0.088 |
| Reader interest | 0.42 | 0.72 | 0.70 | 0.61 | 0.30 | +0.26 | +0.159 |
| Audience breadth | 0.56 | 0.55 | 0.48 | 0.53 | 0.08 | +0.13 | +0.069 |
| Practical relevance | 0.75 | 0.70 | 0.68 | 0.71 | 0.07 | +0.22 | +0.156 |
| Substantiated | 0.87 | 0.45 | 0.95 | 0.76 | 0.50 , above the contested threshold | +0.05 | +0.038 |
| Technical depth | 0.77 | 0.45 | 0.55 | 0.59 | 0.32 | +0.05 | +0.029 |
| New information | 0.91 | 0.95 | 0.98 | 0.95 | 0.07 | +0.05 | +0.047 |
| Promotional | 0.12 | 0.05 | 0.03 | 0.07 | 0.09 | −0.19 | −0.013 |
| Overclaim | 0.19 | 0.10 | 0.04 | 0.11 | 0.15 | −0.11 | −0.012 |
| Sum of contributions | +0.562 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.562 | ||||||
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/136/"><img src="https://rubric.hrih.si/badge/2026-10-28/136.svg" alt="Ranked #136 on Rubric, 28 Oct 2026" width="252" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.