yibie/awesome-jev on GitHub
- Stars
- 1,547
- Forks
- 222
- Language
- Python
- Last push
- 24 Sep 2026
Read from GitHub on . Counts change daily.
yibie’s awesome-jev puts each entry in exactly one category, chosen by the project’s direct Jev application domain. The README is explicit that inclusion means public, citable and genuinely using Jev for a typed decision, not a quality or endorsement judgment, and it warns specifically about same-day bulk submissions from one author sharing a scaffold and thin commit history, which can pass every inclusion rule while still being unproven.
A dedicated category for related practices and discussions covers X threads, Reddit posts and interviews that describe real Jev usage without a standalone project page. The repository also uses Jev on itself. A script, jev-ray.py, asks Jev four typed questions about each linked repository to propose agent and type tags, and a hand-written tag always wins over its proposal. It can call TypeSafe’s API directly or reach Jev through OpenRouter’s decisions endpoint.
How it uses Jev
TAGS_PATH = REPO_ROOT / "tags.json"
DEFAULT_CACHE = REPO_ROOT / ".jev-ray" / "cache.json"
PROVIDERS = {
"typesafe": ("https://api.typesafe.ai/v1/systemone", "jev-latest", "TYPESAFE_API_KEY"),
"openrouter": ("https://openrouter.ai/api/alpha/decisions", "~typesafe/jev-latest", "OPENROUTER_API_KEY"),
}
RETRY_STATUS = {408, 429, 500, 502, 503, 504, 529}
# Same grammar as scripts/build-readme.py: the tag block sits between link and separator.
ENTRY_RE = re.compile(r"^- \[([^\]]+)\]\(([^)\s]+)\)(?:\s*`\{([^}]*)\}`)?\s*-\s*(.+)$")
GITHUB_RE = re.compile(r"^https?://(?:www\.)?github\.com/([^/\s]+)/([^/\s#?]+)")
# The digest is the model's whole view of a repository. ~2k tokens of README is
# the size the issue budgets for; manifests are short and carry install targets.
