Claim your server

Claiming proves you own the repository, and unlocks the author-declared band on your server’s page: safer-mode flags, intended scopes, recommended config, and a badge you can paste into your README.

Claiming

sha256:0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a

cmd:sha256:0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a

Sign in with GitHub to claim

These badges already work today — claiming adds the author band on top.

Adoption

Live count of public repos observed wiring this server up.

ax-ray Adoption badge
[![ax-ray](/badge/cmd/sha256%3A0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a.svg?metric=adoption)](/server/cmd/sha256%3A0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a)
Status

The band this page currently sits in — observed, never a verdict.

ax-ray Status badge
[![ax-ray](/badge/cmd/sha256%3A0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a.svg)](/server/cmd/sha256%3A0131ae2f44f6cd8925ccaaee2ae3f4c39390cd777a5ef24ea652f37d485f016a)
  1. 1

    Prove ownership

    Sign in with GitHub. You can claim any server whose repository is under your account — we match the repo owner to your GitHub login.

  2. 2

    Add context

    Declare safer-mode flags, intended scopes, and recommended config — stated intent, shown as its own band, never blended with static facts.

  3. 3

    Embed the badge

    Copy the Markdown snippet from your page into your README. Every badge links back and reflects your current signals.

Claiming is a public ownership proof, not a contribution — no data leaves your machine.