User repository on GitHub
Chrome extension that re-ranks Google results with TypeSafe Jev and folds away sales pages and SEO filler.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Demos & Experiments
Sift — tylergibbs1
Chrome extension that re-ranks Google results with TypeSafe Jev: five atomic questions per result, a weighted score, sales pages flagged and hidden, and a button to restore Google's order.
- Stars
- 0
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- tylergibbs1
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Sift — bohutang.
About this project
A Chrome extension (Manifest V3) that re-ranks Google results with TypeSafe Jev. It moves results that answer the query to the top. It folds away sales pages and SEO filler. content.ts scrapes the organic results on google.com/search. Sponsored blocks are skipped.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- One Jev call per organic result, all in flight at once, asking four Noul questions and one 0-3 depth Score.
- A result flags at 0.85 promotional or filler probability but hides only above 0.6 depth confidence; otherwise it dims.
- A transactional-intent question spares sales pages on queries like "pizza delivery near me" while research queries still filter them.
- A corner toast reports what changed with Show original and Re-apply, and site rules in chrome.storage.sync apply without an API call.
Watch out
The only evidence sent is the result title, domain, URL and snippet, and the README is explicit that this is weak evidence for whether a page answers the query; fetching the top pages and sending the first ~1,500 characters is described as a possible next step, not something implemented. Only www.google.com is matched, and other Google domains have to be added to static/manifest.json. Scores are cached in chrome.storage.local for 7 days under a hash of the question set, query and URL, so changing a question discards old scores. You need your own TypeSafe API key, entered on the options page and kept in chrome.storage.local rather than synced. The README does not say what a single page view costs in tokens, how many organic results a typical page yields, or what the 0.85 and 0.6 defaults cost in false hides on real queries. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
The README is specific about the mechanics and silent on the cost. Calls run concurrently per page, plus one extra intent question per search; scores are cached in chrome.storage.local for 7 days keyed by a hash of the question set, query and URL, and 429 and 529 responses retry with exponential backoff and jitter. It does not publish tokens per call, results per page, or any rate limit, so you would be estimating before switching this on for every search.
Hiding is deliberately gated twice. A result flags when promotional or filler probability hits flagThreshold (default 0.85) and is hidden only when the depth answer's confidence is at or above hideMinConfidence (default 0.6); below that it is dimmed instead. A result whose scoring failed stays in its original position, site rules can always boost or hide a domain, the Why this rank popover lists every factor and its direction, and Show original restores Google's order exactly.
Probably, and the repo documents the repair rather than pretending it will not happen. Only www.google.com is matched, and all DOM assumptions live in src/serp/selectors.ts. The documented fix is to save a real results page, update test/fixtures/serp.html to match the new markup, then update selectors until test/serp.test.ts passes; CI runs npm run check, which lints, type-checks, tests and builds.
Just the snippet. content.ts scrapes organic results, skipping sponsored blocks, and the evidence per result is the title, domain, URL and snippet. The README lists this under known limits: those fields show sales copy and listicles well but are weaker evidence for whether a page answers the query, and sending the first ~1,500 characters of the top pages is a slower follow-up the author has not built.
npm install and npm run build to produce dist/, then load that folder unpacked in chrome://extensions with Developer mode on, and enter your TypeSafe API key on the options page that opens on install. The key lives in chrome.storage.local, is not in the package, and is not synced.
One Jev call per result asks five atomic questions: four Nouls (answers the query, promotional, SEO filler, discussion) and one depth Score from 0 to 3 normalized to 0 to 1. The answers combine into a weighted score; a result is flagged at promotional or filler probability 0.85 by default and hidden only when depth confidence is at least 0.6, otherwise dimmed, and a failed score keeps its original position.
Yes. Site rules always boost or hide a site; you can set one from a result's badge, a Why here button, or the Sift right-click menu on a result link. Rules sync with chrome.storage.sync and apply without an API call, and an open results page re-ranks as soon as a rule changes.
More Jev resources like this
23GitHub stars
Chrome extension that sends each X post to Jev with six typed questions in one call near the viewport, then renders a behavior chip under the post plus a session cost and latency panel.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
oso95/x-scannerTypeScript
oso95/x-scannerTypeScript2GitHub stars
A Magic 8 Ball that picks with Jev instead of at random. Hold, shake, release, and Jev chooses from the twenty classic answers and returns a probability for each one, shown under the ball.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
mikecann/magic-jev-ballTypeScript
mikecann/magic-jev-ballTypeScript0GitHub stars
JevPlay is a playground for TypeSafe Jev: a freeform state block plus a builder for custom Choice, Score and Noul questions, showing live probability distributions as you write them. Setup is npm i and npm run dev.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
ndolinschi/jevplayTypeScript
ndolinschi/jevplayTypeScript0GitHub stars
A TypeScript CLI and Fastify service that puts three questions about an occupation to Jev in one request - layoff risk, trajectory and human accountability - and derives a resilience score in app code.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
WeSecureYou/Jev-testTypeScript
WeSecureYou/Jev-testTypeScript46GitHub stars
Open 150M encoder that reproduces the typed noul, choice, and score interface in one forward pass, trainable on a free GPU and runnable locally for nothing.
Jev Demos & Experiments#community#jevbest#catalog-import
98GitHub stars
Self-hosted Docker service and web UI that packages Laya structured-decision inference behind a compatible System One endpoint.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
1Panel-dev/laya-serverPython
1Panel-dev/laya-serverPythonFrom the Jev guides
Original write-ups on what this entry is for.
A game tick is a state plus a legal action list. How Clash Royale, Minecraft, and the earlier Mario, Pokémon, StarCraft, and drone loops ask Jev one step at a time.
Jev Demos & Experiments#gaming#agents#control
Read article
From the Jev community
Posts from builders shipping with Jev right now.