PyMolt
Get started
Open numbers

Everything we can measure, published here.

A tool that refuses to guess about your code shouldn't ask you to take its own adoption on faith. The numbers below are whatever they actually are — including the ones that are currently zero.

Live now

refreshed hourly
GitHub stars
—
on the public repository
source: GitHub API, hourly
Libraries in the catalog
26
8 of them with hand-written behavioral rules
source: this repository
Released version
v0.1.0
first public cut
source: pyproject.toml

Not measurable yet

shown so you can see what's missing
PyPI downloads
not published yet
monthly, from the public download dataset
starts when the first release is published
source: PyPI / pypistats
Recipes served
not published yet
how many version pairs the hub answered for
counting from the first public hub deploy
source: hub request log, aggregate only
Distinct packages requested
not published yet
which libraries people actually migrate
counting from the first public hub deploy
source: hub request log, aggregate only
Rules delivered vs. locally verified
not published yet
the share that survives re-checking on real code
needs opt-in reporting, not built yet
source: opt-in only, never automatic
Ad-hoc recipes built on request
not published yet
libraries added because someone asked
counting from the first request
source: issue tracker
Behavior checks run
not published yet
would require telemetry in the CLI
not planned — see below
source: —
How these are counted
  • Public sources — stars come from the GitHub API, downloads will come from PyPI's public dataset. Anyone can reproduce them.
  • Server-side totals — the hub knows how many recipe requests it answered, the same way any web server knows its request count.
  • Nothing per-user — a recipe request carries a package name and two versions. There is no account id attached, so “who asked” is not a question the data can answer.
What is never collected
  • Your source code, file names, or repository layout.
  • Your lockfile, or the full list of packages you depend on.
  • Anything at all from the parts that run locally — scanning, rewriting and the behavior check make no network calls.
  • The CLI ships no telemetry. That is why “behavior checks run” above says not planned rather than soon.

Think a number here is wrong or missing? hi@zeelex.me