Phase-1-MVP in development · Pivot completed 2026-05-26

Which open-source project is used where, how long, and how widely — verifiably anonymously?

Prometheus is a decentralized, fully public platform for anonymous measurement of the usage and reach of open-source software. No central operator, no tenants, no paywall — all accepted aggregates are Open Data.

Contribute → View SDK

4 capture modes 6 SDK languages 14 pipeline stages k ≥ 5 as schema constraint

Overview

Seven topics, one page each.

Prometheus cannot be explained in a single paragraph — but each individual topic can. Start where it affects you.

The Measurement Problem

NPM downloads count packages, GitHub stars count attention. No one measures usage duration and activity systematically.

Why now 02

Four Capture Modes

SDK, End-user Agent, Hybrid Aggregator, and Registry Scraping — in parallel, via an open protocol.

How measurement works 03

Privacy

k-Anonymity is not a promise, but a schema constraint. Two independent PII gates.

How it is guaranteed 04

Benefits by Role

What foundations, vendors, research, and the security community concretely gain from this.

For decision makers 05

For Developers

Six SDK languages, byte-identical canonical output, a very small runtime budget.

SDK & Protocol 06

Roadmap

Three phases: Reach & Runtime MVP, Federation with ZK-Attestation, Threshold Consensus.

What's coming when 07

Contribute

Needed: mirror hosting, a pilot library, research partners, legal review — no capital.

What is needed

Principles

Four commitments that are non-negotiable.

They are not only in the documentation but enforced in the schema and pipeline. A violation is an auto-FAIL in review.

k-Anonymity as Schema Constraint

Default k ≥ 5, for modes B and C k ≥ 25. Cohorts that are too small are rewritten locally before anything leaves the machine.

PII never on Disk

Raw events reside exclusively in RAM or tmpfs. Only already signed aggregates are written to disk.

Open Data by Default

No tenant separation, no paywall, no login for read access. Daily snapshots as Parquet and CSV.gz.

Verifiability over Trust

Each accepted submission lands as a hash in the public Sigstore Rekor log and can be verified externally — from day 1 of mirror operation.