What it is
Personalize offers from intent signals without hoarding browse history on the server.
What it does: Browser-held history + hosted Jev decision API for offer selection.
Why it belongs in the showcase: Documented JP personalization stack with explicit Jev adapter.
Caveats: JP docs; JEV_API_KEY naming.
Evidence
Public MIT repo with Japanese README/docs, created 2026-10-29, 0 stars as of 2026-11-02. docs/design.md states Jev adapter with Bearer auth, fixed version, JEV_API_KEY, 1.2s Jev timeout, admin debug panel without shipping keys to sites, plus live admin URL. Deferred from 2026-10-30 for deeper hosted-client verify; naming is JEV_API_KEY but adapter targets hosted Jev.
Caveats
- Docs and admin UI are primarily Japanese
- Env var is named JEV_API_KEY (not TYPESAFE_API_KEY)—confirm against your TypeSafe console
- 0 stars; production needs Cloudflare secrets / ops setup
Unofficial case page. Stars / list position observed for heat; do not treat heat as a quality SLA. Review the upstream README before you depend on it.