Evidence is selected, not generated
Jev chooses line IDs from the two reports; code copies those lines verbatim. This constrains invented quotations but does not prove the interpretation is right.
Inspect the supporting source ↗REPOSITORY ANALYSIS
jev-issue-radar
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.
E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
- Stars
- 1
- Forks
- 0
- License
- MIT
- Last commit
- 2026-09-20
What Jev does here
The app never closes issues, posts comments, or changes labels. Retrieval is currently lexical and bounded to a recent-item scan; this limitation is explicit in the UI and README.
Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.
Review scope is the pinned README protocol: lexical candidates, selected evidence-line IDs and failed comparisons. This site did not scan GitHub or rerun the author’s four-pair integration test; constrained quotations do not prove duplicate recall.
What task does this project fit?
Help maintainers review potential duplicate GitHub issues without modifying the repository.
Material analysed：
From input to action
- Retrieve recent lexical candidates.
- Ask four Choice questions for relationship, evidence IDs and reason.
- Display a strong duplicate label only when local evidence and confidence rules agree.
Implementation details that matter
Retrieval and classification fail differently
Lexical retrieval can miss cross-language or differently worded duplicates before Jev sees them. Provider errors remain failed comparisons, not distinct verdicts.
Inspect the supporting source ↗When to choose it
Choose this for a review queue where a maintainer can inspect source passages. It is not an automatic issue-closing agent or proof of high duplicate recall.
How to inspect it yourself
Inspect lib/jev.mjs for the alpha Decisions endpoint and max-call controls in the README. Compare the hand-authored demo with the separately attributed 2/4-label integration result.
Limits of this review
- No independent GitHub scan or live model call was run.
- The author's four synthetic integration pairs are too small to establish general accuracy.