Skip to main content

CLI Telemetry

What the Repotoire CLI collects when you opt in

Overview

Repotoire collects anonymous usage data from CLI users who explicitly opt in. This data helps us improve the tool and powers ecosystem benchmarks — so you can see how your project compares to others.

Telemetry is off by default. You must explicitly enable it. You can disable it at any time.

What we collect

Analysis data

  • Score, grade, and pillar breakdowns (structure, quality, architecture)
  • Finding counts by severity, detector, and category — not the findings themselves
  • Graph metrics: node/edge counts, modularity, circular dependencies, coupling
  • Repo shape: workspace/monorepo detection, language breakdown, lines of code
  • Detected frameworks (e.g. "django", "actix-web")
  • Calibration threshold divergence from defaults
  • Analysis duration and mode (cold/incremental/cached)

Usage data

  • Which commands you run and how long they take
  • Fix acceptance/rejection per detector
  • True positive/false positive feedback labels
  • Watch session duration and reanalysis counts
  • Diff score deltas

System info

  • Operating system (linux/macos/windows)
  • Repotoire version
  • Whether running in CI

What we never collect

  • Repository names or URLs
  • File paths or code content
  • Git author names or emails
  • API keys or credentials
  • IP-based geolocation (disabled in our analytics provider)

How it works

Each CLI install gets a random anonymous ID (UUID). Each repository gets a one-way hash (SHA-256 of the root commit) — we can track trends for the same repo without knowing what repo it is.

Events are sent to our analytics backend. A scheduled job computes aggregate benchmarks and publishes them as static JSON. Your CLI fetches these to show ecosystem comparisons.

Managing telemetry

repotoire config telemetry on      # enable
repotoire config telemetry off     # disable
repotoire config telemetry status  # check current state

Environment variable overrides:

  • REPOTOIRE_TELEMETRY=off — disable per-invocation
  • DO_NOT_TRACK=1 — industry standard, always honored

What you get back

With telemetry enabled, after every analysis you see:

  • Your score percentile among similar projects
  • Pillar comparisons (structure, quality, architecture)
  • Graph health benchmarks (modularity, coupling)
  • Detector accuracy rates from community feedback

Run repotoire benchmark for the full comparison.