Sources and evidence

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.

Discovery sources

• awesome-jev — source
• typesafe-field-guide — source
• GitHub repository search — source
• Official TypeSafe repositories — source
• Approved editorial submissions — source

Community directories supply 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 searches are disclosed in the report.

Updates and corrections

A Cloudflare scheduled worker advances small batches every minute and refreshes community feeds every six hours. Failed individual checks retain the last known result with a stale label. Unavailable repositories are retained for rechecking. Editors may approve, reject, reclassify or withdraw submissions. Approvals are queued in D1 and appear after the worker checks their evidence; pages read the live catalog.

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