Skip to content

Releases and install counts

This page explains how a release is built and how installs are counted without telemetry. In short: the plugin ships as a zip on a tagged GitHub release, and GitHub’s download count for that zip is the measure (DECISIONS.md D69).

Why not ask Claude Code for install counts?

It has none to give. Its documentation says: “Claude Code doesn’t report a plugin’s usage back to its author.” Public install counts exist only for the claude-plugins-official marketplace.

What else was considered?

optioncountsnot chosen because
a ping from the pluginanythingit is telemetry; the product does not phone home
marketplace.json served from our own URLadds and every refreshalso fetched on update and on install-by-name; our domain becomes a supply-chain point
GitHub clone trafficunique clonersa 14-day window; mixes refreshes, updates and CI
release zip, archive sourcezip downloadschosen

How is a release made?

A tag v<version> runs .github/workflows/release.yml:

  1. typecheck and the test suite
  2. a check that the tag matches the version in .claude-plugin/plugin.json and package.json
  3. scripts/build-release.sh builds the zip of the runtime files (marketplace.json stays out, because it holds the zip’s hash)
  4. a GitHub release is created with the zip attached
  5. only then, a commit points the marketplace.json entry at the zip, with its sha256

The hash is taken from the uploaded bytes, never from a rebuild, so a changed zip fails to install. If the last step fails, the entry keeps its previous source. The install command does not change.

A release requires Claude Code 2.1.224 or later, the version that added the archive source.

What does one download mean?

eventdownloads the zip
first installyes
installing again on the same machineno, unless the cache is gone
marketplace refreshno: that clones the repo for marketplace.json
updating to a new versionyes
background auto-updateoff by default for marketplaces other than Anthropic’s

So the count is first installs plus manual upgrades, per release. GitHub does not deduplicate, so it is not a count of people.

The full reasoning, with the documentation quoted, is in docs/distribution.md.