Show HN: Open-Source Greptile Alternative
npx juror-ai review --pr 1234 N frontier models review your PR in parallel, each through its own native agent harness. Reports about the same defect collapse into one. Add it to your repo Three steps, about two minutes.
- ▪npx juror-ai review --pr 1234 N frontier models review your PR in parallel, each through its own native agent harness.
- ▪Reports about the same defect collapse into one.
- ▪Add it to your repo Three steps, about two minutes.
Hacker News (Front Page) files mainly under programming. We currently carry 1,381 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/Juror-AI/juror |
| Publication time | Mon, 10 Aug 2026 14:17:13 +0000 |
| Retrieval time | 2026-08-10T16:15:47.885Z |
| Last seen | 2026-08-10T16:15:47.885Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | DL_DV0fpQG6y · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
npx juror-ai review --pr 1234 N frontier models review your PR in parallel, each through its own native agent harness. Reports about the same defect collapse into one. Every review prints its own receipt. Add it to your repo Three steps, about two minutes. No app to install, no account to create, no repository index to build — it runs on your own GitHub Actions runner, and your code never leaves it beyond the model API call itself. 1 — Drop in the workflow. Save this as .github/workflows/juror.yml: name: Juror on: pull_request: types: [opened, synchronize, reopened] permissions: contents: read pull-requests: write jobs: review: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 with: { fetch-depth: 0 } # full history: review policy is read from the base revision - uses:…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.