Store guidelines

The rules every community extension in the Ingot store follows: honest listings, safe packages, clear names, and versions people can trust. The store checks what it can automatically; the rest is up to you, and listings that break these rules are taken down.

Be honest about what it does

  • Describe what the extension does today. No roadmap items, no "coming soon".
  • No made-up numbers. Manifests can't carry download counts, installs, ratings, reviews or stars, and the store never shows any.
  • Keep the description to one line (200 characters) and put the details in README.md, which is shown on the store page.
  • Show how to use it. Say what to do after installing: which theme to pick, which command to run, which tools the server adds.

Names and branding

  • Pick a name and displayName that describe the extension. Don't use the names of other products in a way that suggests they made it ("Official GitHub Theme").
  • Don't use Ingot or Zaprex branding, logos or the words "official" or "verified". Publisher handles that look official are reserved.
  • Don't upload other people's logos. The store shows a colored tile with 1 to 3 characters (icon in ingot.json).
  • Community listings show a Community badge. Only Ingot and Zaprex are verified publishers.

Safety

  • No secrets in packages. Never ship API keys, tokens or passwords. For MCP servers, describe each variable in env and let users fill in their own values.
  • No hidden behavior. An MCP server or command must do what its README says. No tracking, no sending code or data anywhere the user didn't ask for, no mining, no obfuscated code.
  • Pin what you run. MCP servers started with npx should name an exact package (and ideally a version), not a URL or a script piped to a shell.
  • Ask before destroying anything. Commands and Rex templates must not delete files, force-push or touch production systems without the user asking.
  • Rules are instructions, not attacks. Rules and templates must not try to make the agent ignore the user, hide changes or exfiltrate data.

The store validates every upload (manifest, paths, file types, sizes, JSON and regular expressions) but it doesn't run or review your code. Users see a note saying so on every community page.

Licensing

  • Set license to an SPDX id and include a LICENSE file (ingot init writes an MIT one).
  • Only publish what you have the right to publish. Themes ported from other editors must keep the original license and credit.

Versions

  • Use semantic versioning: bump the patch version for fixes, minor for additions, major for changes that break existing setups.
  • Every upload needs a new, higher version. Version numbers are never reused, even after an unpublish.
  • Keep CHANGELOG.md up to date; ingot version adds the heading for you.
  • Unpublish a broken version and publish a fix rather than leaving it up.

Takedowns and reports

To report an extension that breaks these rules (or your rights), use Report this extension on its store page or contact support with the extension id (publisher.name). Ingot may unpublish an extension, revoke its publisher's tokens, or close a publisher account that breaks the rules or the acceptable use policy.

Before you publish

  • ingot validate passes
  • you tested it with ingot try in a real project
  • the README explains what it does and how to use it
  • no secrets, keys or personal data in any file
  • license, LICENSE and CHANGELOG.md are set
  • the version is new and follows semver