rulepackdocs
Legal & policies

Name & verification policy

How scope names are protected, claimed, verified, and disputed.

Last updated: 2026-06-02

Scope names (@scope) should belong to the people and organizations they represent. This policy explains how rulepack protects well-known names, how the rightful owner claims one, what the verified badge means, and how to dispute squatting or impersonation. It supplements the Acceptable Use Policy.

Two kinds of held names

  • Reserved — system/route names (admin, api, docs, …) and names kept for the project. Not claimable by anyone.
  • Protected — well-known library, company, and product names (e.g. react, vercel, openai). Held back so they can't be squatted, but released to the verified rightful owner through the process below.

If you try to claim either, scope creation is declined with a pointer here.

The verified badge

A verified scope (checkmark) has been confirmed by the maintainers to represent the real person or organization behind the name. It's granted when a protected name is released to its owner, and may be granted to other scopes we can confirm. It is a trust signal, not an endorsement of any pack's contents.

Claiming a protected name / requesting verification

Claims go through an in-app support ticket on the name dispute channel — a private thread with the maintainers, tracked in your account:

  1. Open a ticket at /support and choose Name dispute / takedown. Trying to claim a protected name links you straight there with the scope prefilled.
  2. Tell us the scope you want, who you represent, and how we can verify it — e.g. you're an owner of the matching GitHub organization, you control the project's official domain or repo, or another public proof.
  3. We review, and if confirmed, assign the scope to your account and grant the verified badge.

Prefer email for something you can't share in-app? Write to [email protected] — but a ticket is preferred for name matters so the whole thread stays in one place.

One account, one scope

Each account owns a single scope, so an organization's verified scope lives on a dedicated account (the one we assign it to). Plan to use an account that doesn't already own another scope.

Disputing squatting or impersonation

If a scope or pack impersonates you or squats your name:

  • Use the Report button on the pack page, or open a support ticket, or email us.
  • Include the scope/pack and how it infringes (trademark, identity, project name).
  • We review against this policy and the Acceptable Use Policy. Confirmed squatting or impersonation can lead to the name being reclaimed and reassigned to the rightful owner, and the offending content removed.

We act on good-faith reports and may request reasonable proof of ownership.

Contact

Edit on GitHub

Last updated on

On this page