Legal and safety

Content policy

These rules keep the Registry useful, attributable, lawful, and safe to install. They apply to packs, assets, previews, public copy, profiles, requests, and engagement.

Effective July 23, 2026

01

Rights and provenance

Only publish work you created or are permitted to redistribute. Asset records must name the source, rights holder, and exact permission. A reference image is not redistribution permission.

02

No deceptive affiliation

Do not imply that a theme is official, sponsored, endorsed, or created by a person or organization without evidence. Brand-inspired themes must remain clearly unofficial.

03

Safe, useful content

No malware, executable pack hooks, credential collection, harassment, sexual exploitation, graphic violence, hateful content, doxxing, or instructions intended to cause harm.

04

Honest previews and copy

Previews must represent the submitted theme and remain privacy-safe. Taglines, descriptions, and design stories must be factual, distinct, and free of spam, hidden text, keyword stuffing, or fabricated claims.

05

Authentic community activity

Do not manipulate downloads, likes, votes, requests, creator identity, or rankings. Automated traffic and coordinated inauthentic engagement may be removed from counts or blocked.

06

Creator identity

GitHub attribution is linked through sign-in. X attribution is a publisher-provided public profile URL and is labeled accordingly. Impersonation, contested identities, and misleading usernames may be suspended.

Enforcement

We may reject, delist, restrict, or remove content; discount manipulated engagement; suspend an identity; preserve evidence needed to investigate a report; and prevent repeat abuse. Automated validation reduces risk but does not guarantee that every issue is detected.

If you believe content violates this policy, use the private report form. For copyright and legal removal requests, follow the takedown process.

PUBLISHER ACCESS

Sign in to
share your work.

Use an identity you already trust. We only use it for contributor attribution and publishing access.

No password or email registration. Your provider verifies your identity.