JevHunt

Sources and evidence

JevHunt uses GitHub Repository Search as its primary discovery path and supplements it with community feeds, official repositories and approved submissions. Coverage is broad but cannot be guaranteed exhaustive.

What each label means

  • Official: an allowlisted SDK or resource owned by TypeSafe.
  • Documented: first-party documentation states a Jev use or includes an API / SDK reference.
  • Code reference: a Jev API identifier was found in source, linked at a specific commit.
  • Editor reviewed: an editor checked the linked source and project classification.
  • Needs review: retained historical data awaiting a successful new check.

These labels do not mean we executed the code, audited its security or reproduced its performance claims.

Project types

Applications, optional integrations, SDKs, local alternatives, research and resource directories have separate labels. A local alternative may reproduce the decision interface without calling TypeSafe Jev. Classification is based on project descriptions and source documentation and can be corrected by editors.

Reviewed project explanations

The first 100 projects have source-backed explanations in all 15 supported locales. Each covers the project purpose, the actual role of Jev, how to begin and material limits, with links to commit-pinned source passages. These explanations were drafted with AI assistance and separately checked by models for source fidelity and language. This is not native-human language review or a runtime test.

Project-name and task-based search intents are editorial hypotheses, not measured rankings or traffic. Source changes enter a review queue; repository metadata can update independently while explanations retain their stated source-review date.

Discovery sources

  • GitHub repository search — source: jev in:name,description,readme fork:false
  • GitHub repository search — source: typesafe in:name,description,readme fork:false
  • GitHub repository search — source: "TypeSafe Jev" in:readme fork:false
  • GitHub repository search — source: "@typesafe-ai/sdk" in:readme fork:false
  • GitHub repository search — source: "typesafe-sdk" in:readme fork:false
  • GitHub repository search — source: "jev-latest" in:readme fork:false
  • GitHub repository search — source: "system one" in:readme,description fork:false
  • GitHub repository search — source: "TYPESAFE_API_KEY" in:readme fork:false
  • GitHub repository search — source: topic:jev fork:false
  • awesome-jev — source
  • typesafe-field-guide — source
  • Official TypeSafe repositories — source
  • Approved editorial submissions — source

GitHub Search queries cover repository names, descriptions, README references, topics, SDK identifiers and model identifiers. Community directories add discovery links. Current metadata comes from GitHub. README and source references are pinned to commits. Search pages are partitioned by creation date when GitHub's 1,000-result limit is reached; partial results and request counts are disclosed in the audit report.

Updates and corrections

Catalog information changes only when an editor runs a manual update. Each project retains its last known information and check date. Today’s picks rotate 1–8 existing projects each day; selection is not a new launch or a new source check. Editors review corrections and submissions on GitHub.

Update status · Machine-readable audit report · Catalog JSON · Report a correction