~ $ chasen stats

Stats.

GitHub's public counters for the CLI and server, and how often we ship. No telemetry, no tracking—these numbers come from GitHub's API only.

[01] at a glance

CLI installs

—

chasen-(linux|darwin)-* assets

Releases (30 days)

—

shipped this month

Days since release

—

to latest version

Latest

—

[02] cli per release

Downloads by version.

Each release's downloads of the CLI: Linux below, macOS on top. Hover a bar for its numbers.

[03] releases over time

How often we ship.

Releases per week since the first release.

— total releases— median between releases

[04] commits (52 weeks)

Development activity.

Commits per week for the last year.

[05] recent releases

The last 8 versions.

[06] github

Community and maintenance.

—

Stars

Star it on GitHub → It is the one number here that only people move.

—

Open issues

Bugs, features, and questions waiting.

[07] how we count

Transparency.

Chasen collects no telemetry. The CLI and the server do not send any data about usage, errors, or user behavior.

All numbers here come from GitHub's public API. Download counts are the download_count field of each release asset. Release counts, activity, stars, and open issues are GitHub's own counters.

When the CLI checks GitHub for a new release (once a day, by default), that check is not counted in the download stats. GitHub's API records only downloads of release assets, not API requests.

The server download count includes nightly self-updates. Each server downloads every release during its automatic update job, so that number grows with the number of releases, not with the number of servers. It is a measure of how often we ship, not how many servers run Chasen.

This page fetches the GitHub API in your browser, caches the results in sessionStorage, and updates them each time you visit. It fails soft: if GitHub does not answer, the numbers show "—" and you can still read the page.