2 items
See which lines in any GitHub repo are hardcoded guesses that should be a Jev judgment, with a fit score for each. Read-only. JevX finds the judgment calls hiding as rules in code: regexes that guess what an error means, keyword lists that guess what a customer wants, includes() checks that guess intent. Open any GitHub repository, click JevX, and get: The exact file and lines where Jev fits The current code, and the question Jev would ask instead A fit score from your AI, patterns from real Jev projects, and TypeSafe (optional) A plain verdict: "Jev fits here", "could help", "mixed signals" or "not needed" A ready prompt for Claude or a JevX command to apply the change locally, with your tests running before and after Bring your own AI key: Gemini, xAI (Grok) or OpenRouter. Private by design: read-only, keys stay in your browser, code goes only to the AI provider you choose, and secrets are removed first. No tracking, no analytics. Open source (MIT): https://github.com/vij-sameerb5/JevX Website: https://jevx.live
Oct 5, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.