jevbooks

← All projects

open-source-finder

Tanishk901/open-source-finder

Ranks GitHub open issues for first-time contributors using Jev.

Scoring & Ranking1.00Runner-up: Classification & RoutingQuestionnaireTraffic light
Automated README summary

Automatically summarized from the README on 24 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A Python CLI that scans any public GitHub repo's open issues and ranks them by how small, clear, and self-contained they are, flagging issues someone already claimed. Aimed at first-time open-source contributors.

How it uses Jev

Each issue is sent to Jev in one request with five parallel questions: scope and clarity and context_needed as Score levels, actionable and claimed as Noul yes/no. Plain code in rank.py turns the answers into a Beginner score, size, and flags.

Primitives:scorenoul

Technique worth stealing

Ask one model several narrow typed questions in parallel per item, then rank with plain deterministic code and tuned thresholds.

Try it

git clone the repo, create a venv, pip install -e ., add TYPESAFE_API_KEY to .env, then run open-source-finder scan owner/name.

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.14.0
Project signals
jev-1.14.0
Category
jev-1.14.0
Pattern tags
jev-1.14.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.86
  • Shows a System One patternnot found in the excerpt0.07
  • Describes handling uncertaintynot found in the excerpt0.03
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolFound in material0.65
  • Top-10 learning shortlist signalnot found in the excerpt0.18
  • Is a replica of the modelnot found in the excerpt0.07
  • Solves a common problem (0–2)score on a 0–2 scale1.20 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.86Shows a System One pattern0.07Describes handling uncertainty0.03Reports measured numbers0.04Is a runnable tool0.65Top-10 learning shortlist signal0.18Is a replica of the model0.0700.51Solves a common problem (0–2)1.20 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.98Traffic light0.93Funnel0.66Scorecard0.56Question bank0.40Blind review0.39Grey zone0.39Flight recorder0.33Viewfinder0.2500.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 24 Oct 2026.