Overview
jev-semgrep is uehaj's meaning grep CLI. You state a natural-language proposition; the tool batches lines from stdin or files and asks Jev whether each line satisfies that meaning above a threshold. AND, OR, and NOT compose propositions; file language and query language can differ.
Problem: Regex grep misses intent (find the line that handles refunds) and LLM grep burns budget reading whole files into chat.
Built for: Developers who want line-level semantic filters in CI or ad hoc audits with composable boolean meaning expressions.
First indexed on Jev Directory: 2026-09-22
Creator and team
- Name
- uehaj
- Handle
- @uehaj
How Jev is used
- Role in the product flow
- Per-line semantic match filter (batched Noul questions)
- Primitives
- Noul
- State in
- One text line (or batch) plus the active meaning proposition from the CLI expression tree.
- Decision out
- Binary keep or drop for each line based on calibrated probability against threshold; composed trees for AND/OR/NOT.
- Parse CLI meaning expression (possibly nested boolean ops)
- Stream or batch file lines to Jev with the active proposition
- Threshold Noul outputs to emit matching lines only
- Cross-language: proposition can be Japanese while the file is English, per author writeup
This is grep-shaped, not agent-shaped. Every emitted line earned its place because Jev answered a Noul question: does this line entail the meaning you asked for? Batching keeps latency tolerable on large repos. Boolean composition lets you build mini policies (error handling AND not test fixture) without learning another query DSL beyond words. The Zenn article walks through real examples and contrasts the approach with classic semgrep rules that die on paraphrase. Bring a TypeSafe key; there is no cloud-hosted meaning grep service in the repo.
Features and stack
Features
- Natural-language propositions instead of regex
- AND, OR, NOT composition in the CLI
- Cross-language matching between query and file
- Line-at-a-time threshold filtering
Stack
- TypeScript
- CLI
- TypeSafe System One
Pricing: Per-line Jev calls; tune batch size and threshold to control cost on big trees.
Links
FAQ
- Is this the Semgrep security product?
- No. The name is a pun on grep-by-meaning. This repo is uehaj's Jev CLI, not semgrep.dev rule packs.
- Which primitive does each line use?
- The README and Zenn post describe a probability that the proposition holds, which maps to Noul semantics in Jev vocabulary.
Related learn guides
Original Jev guidance that pairs with this product pattern.
- Jev use cases
The patterns builders actually search for: moderation, routing, triage, RAG verify, and agent gates.
- System One model
The model family behind Jev: parallel typed questions, one forward pass, probabilities you can threshold.
Related products
Hand-picked neighbors with rich profiles or overlapping tags.