Top Repos· Jev-Based· Demo· Last updated 2026-09-21

uehaj / jev-semgrep

“grep by meaning, across languages. TypeSafe Jev scores every line against a meaning; combine meanings with AND/OR/NOT. 意味で探す grep。日本語で英語を、英語で日本語を検索できる”

Jev-Based rank #27In Demo #6

• 121Stars
• —Stars Δ / 1d
• —Stars Δ / 7d
• —Stars Δ / 30d
• 6Forks
• 1Watchers

GitHub ↗Official docs ↗Back to ranking

TL;DR

uehaj/jev-semgrep showed up as Jev / System One related work: Runnable demo or product experiment that uses Jev as a decision layer.

The author describes it as: “grep by meaning, across languages. TypeSafe Jev scores every line against a meaning; combine meanings with AND/OR/NOT. 意味で探す grep。日本語で英語を、英語で日本語を検索できる” That is their claim, not a bench this site ran.

Who it’s for

• Code-review and context-pruning workflows that must stay schema-bounded
• Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe

What’s inside

Top-level entries on GitHub at generation time: .gitignore, CHANGELOG.md, LICENSE, README.ja.md, README.md, RELEASING.md, docs, package.json, scripts, semgrep.mjs, tests. Read those before you trust a one-line install.

How to use

1. Clone and follow the author’s JavaScript toolchain. Do not invent a package name.

git clone https://github.com/uehaj/jev-semgrep.git
cd jev-semgrep

2. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
3. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "uehaj/jev-semgrep", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Bound a review gate

Using uehaj/jev-semgrep, draft one Choice question: keep / summarize / drop this tool result. State must include the command, the first 2k of output, and the original user task.

Schema-safe ≠ correct

On a case uehaj/jev-semgrep gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.