Skip to content
View and-1991's full-sized avatar
🎯
Focusing
🎯
Focusing

Achievements

Achievement: YOLOAchievement: Pull Sharkx2Achievement: Arctic Code Vault Contributor

Achievements

Achievement: YOLOAchievement: Pull Sharkx2Achievement: Arctic Code Vault Contributor

Block or report and-1991

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
and-1991/README.md

Hi, I'm Jura

Software engineer building Eventra after work - a feature-analytics platform for understanding which features people actually use.

Website SDK npm CLI npm CLI Vue plugin npm CLI Svelte plugin npm CLI Astro plugin npm CLI Angular plugin npm

What is Eventra

Most products accumulate features nobody's sure are still used. Someone asks "can we kill this?" in a planning meeting, nobody has a real answer, and the feature survives another quarter out of pure uncertainty.

Eventra removes the guessing:

  • SDK reports what actually happened - real usage, from inside your app.
  • CLI statically scans your code for what exists - every place a tracked event is reachable, via real compiler-based analysis (TypeScript compiler API + a plugin per framework), not a regex.
  • Dashboard cross-references the two and flags the gap: features that exist in code but haven't fired an event in N days. That's the dead-feature list.

Already using PostHog, Segment, Amplitude or Google Analytics 4? The CLI reads those calls too (and your own tracking wrapper), so you get a feature catalog without re-instrumenting anything. eventra init sets it up.

No runtime magic. No monkey-patching. It reads source code, it reads events, and it tells you where those two things disagree.

Ecosystem

Package What it does Repo npm
SDK Track feature usage in your app (browser, Node, edge, serverless) repo npm
CLI Statically scan your codebase for tracked events repo npm
CLI Plugin - Vue Vue/Nuxt SFC support for the CLI repo npm
CLI Plugin - Svelte Svelte/SvelteKit support for the CLI repo npm
CLI Plugin - Astro Astro support for the CLI repo npm
CLI Plugin - Angular Angular for the CLI repo npm
Dashboard The analytics platform itself - eventra.dev
Examples Full working example projects - frontend, backend, edge runtimes repo -
Docs Code snippets for quick integration repo -

Status

Component Status
Dashboard Production-ready - customizable Overview grid, shared filters, redesigned pages
SDK Stable - batching, retry + backoff, circuit breaker, idempotent delivery
CLI Stable - semantic analysis, wrapper propagation, monorepo support, reads PostHog / Segment / Amplitude / GA4 calls, plugin ecosystem for Vue / Svelte / Astro / Angular

Tech stack

TypeScript Node.js Next.js React NestJS PostgreSQL Prisma Redis Tailwind Docker

Links

Pinned Loading

  1. eventra-sdk eventra-sdk Public

    Analytics client for feature usage: batching, retries with backoff, idempotency keys, circuit breaker. Browser, Node, edge and serverless.

    TypeScript 1

  2. eventra-cli eventra-cli Public

    Static analysis that lists every analytics event in your TypeScript/JavaScript code, including wrappers and props. Finds features that exist in code but never fire. Optional PostHog, Segment, Ampli…

    TypeScript 1

  3. eventra-cli-plugin-vue eventra-cli-plugin-vue Public

    Eventra CLI plugin: finds tracking calls in Vue single-file components, including props passed down to a tracking call.

    TypeScript

  4. eventra-examples eventra-examples Public

    JavaScript