Org and Namespace Claims

ClawHub treats owner handles, org handles, skill slugs, plugin package names, and package scopes as public namespaces. When a namespace appears tied to an actual project, brand, package ecosystem, or organization but is already claimed, reserved, misleading, or contested on ClawHub, request staff review using the Org / Namespace Claim issue form.

This channel is intended for public, non-sensitive ownership evaluation. Avoid using in-product reports or the account appeal form for namespace claims.

When to Open a Claim

Submit a namespace claim if you believe ClawHub staff should determine whether a namespace ought to be reserved, transferred, renamed, hidden, quarantined, aliased, or otherwise modified due to real-world ownership.

Typical scenarios include:

an org handle matching your GitHub organization, project, company, or community
a package scope like @example-org/* that should only publish under the corresponding ClawHub owner
a skill slug or plugin package name that seems to imitate a project
a brand, trademark, project rename, or package history disagreement
a deleted, inactive, or unreachable owner preventing the legitimate namespace owner from taking control

If the listing is unsafe, malicious, or deceptive beyond the ownership conflict, also consult the relevant moderation or security procedures. The namespace claim form handles ownership review only, not emergency vulnerability disclosure.

Before You File

Before filing a claim, verify that you are publishing with the owner matching the namespace. For plugin packages, scoped names like @example-org/example-plugin must be published under the corresponding example-org owner.

If you have access to manage the current owner, resolve the namespace directly by publishing, renaming, transferring, hiding, or deleting the affected resource. File a claim only when you cannot administer the current owner or when staff must settle a dispute.

Evidence to Include

Provide public, non-sensitive evidence. Useful proof includes:

GitHub organization, repository, release, or maintainer history
official project documentation that references the namespace
domain or official email-domain verification
npm, PyPI, crates.io, or other package registry scope control
trademark, brand, or project ownership evidence suitable for public discussion
source repository history, package history, or public rename announcements
links to the disputed ClawHub owner, skill, plugin, package, or issue

Explain what each piece of evidence demonstrates. Staff should be able to grasp the connection without requiring private credentials or secrets.

What Not to Include

Avoid placing secrets or private proof in a public GitHub issue. Exclude:

API tokens, signing keys, or credentials
DNS challenge tokens
private legal documents or contracts
personal identification documents
private emails, private security reports, or confidential customer data

The claim form asks whether sensitive evidence requires a private staff channel. Select that option rather than posting sensitive material publicly.

Possible Outcomes

Based on the evidence and associated risk, ClawHub staff may reserve a namespace, transfer ownership, rename a resource, hide or quarantine an existing listing, add an alias or redirect, request additional proof, or deny the request.

Namespace review does not guarantee that every matching name will be transferred. Staff weigh public evidence, existing usage, security risk, and user impact.