jev-issue-radar
Read-only GitHub dashboard where Jev classifies candidate issue pairs as duplicate, related, distinct or underdocumented, with evidence.
Overview
Jev Issue Radar finds likely duplicate GitHub issues and shows the evidence side by side. Given an issue URL, it retrieves a small candidate set using title-weighted lexical overlap, asks Jev via OpenRouter four Choice questions per pair (relationship, reason and evidence selection), and displays the selected passages from both reports. The model picks a relationship and evidence IDs; the maintainer decides. It never closes issues, adds labels or posts comments.
It is an experimental MVP with no production dependencies or build step, running on Node 22+. A public demo uses four synthetic reports with hand-authored decisions and needs no key. The README is candid: in a four-pair synthetic smoke test two relationships matched expectations, and in a check of three public duplicate pairs none of the canonical issues reached the top five because they fell outside the recent-300 retrieval window, a retrieval limit rather than a classification result.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Are these two issues duplicate, related, distinct or insufficiently documented? | duplicate · related · distinct · insufficient |
| Choice | Which passages are the evidence for that relationship? | — |
How it works
- Enter an issue URL
- Retrieve candidates by lexical overlap
- Ask Jev to classify each pair and select evidence
- Show passages side by side for the maintainer
Strengths
- Read-only; never modifies issues
- Evidence shown from original reports
- No dependencies or build
Caveats
- Detection quality on real repositories not established
- Retrieval limited to recent issues
Getting started
Try the demo at https://patrick-sch03.github.io/jev-issue-radar/ or run locally with Node 22+ and an OpenRouter key.At a glance
- Type
- App
- Status
- prototype
- Language
- JavaScript
- Runtime
- Node 22+ local dashboard
- Has code
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
Jev Issue Radar is a read-only dashboard for GitHub duplicate-issue triage. It retrieves likely candidates, asks Jev whether each pair is duplicate, related, distinct, or insufficiently documented, and shows selected passages from both original reports for a maintainer to review.
logicrw/awesome-jev-projects
Frequently asked questions
What does Jev decide?
The relationship between two issues and which passages support it.
Will it close duplicates?
No, it is read-only; the maintainer decides.
How well does it work?
Not yet established on real repositories, per the README.
Related projects
Open-source team agent platform for Slack, GitHub and more that asks Jev once per session which agent runtime and model to use.
ServicebetaTypeScriptGitHub Action that triages issues with Jev, applying label, spam, needs-info and duplicate tags only above set thresholds.
ProjectbetaTypeScriptSelf-hosted Next.js API and GitHub Actions workflow that has Jev pick one label for each new issue or pull request.
ServicebetaTypeScriptProbot GitHub app that classifies, scores, checks completeness and dedupes issues and PRs with Jev, routing uncertain ones to humans.
ProjectbetaTypeScriptOne YAML task to classify, route, score or verify text with rules, Jev, NanoJev or an OpenAI-compatible model, with cost records.
CLIbetaPythonSmall Python framework and GitHub Action for Jev-powered workflows, with issue triage and PR screening built as examples.
ProjectbetaPython