## Where to report

A public contact route is not available yet. The checklist below helps you collect a useful report; keep it locally until a reporting destination is published.


## What to include

Start with the component page, what you expected and what happened. Add the details below when you have them; a clear reproduction is more useful than a long report.

- **Component identity:** component id, exact version and variant id.
- **Artifact digest:** the `artifactDigest` from the receipt (`bundle.json` or `manifest.json`), which proves exactly which files you started from.
- **Your environment:** Svelte, SvelteKit and Tailwind CSS versions, browser, and whether the problem occurs during server rendering or in the browser.
- **Steps to reproduce**, what you expected, and what happened instead.
- **Whether you edited the source.** If you did, check whether the problem also happens with the unmodified files.

For MCP or API problems, include the tool or route, the input you sent, the error `code` you received, and any request identifier returned with the error.

## Please do not include

- Credentials, API keys, tokens or environment files.
- Personal data about your users.
- Your full project source. A minimal reproduction is more useful.

## Security problems

If a problem could affect the security of people using a component or the catalogue services, do not publish exploit details in a public report. Use a confirmed private contact route before sharing sensitive details. If no route is available, keep those details private.

## Kinds of problems worth reporting

- A component that uses a package or service it does not declare.
- Files missing from a bundle or not matching their recorded checksums.
- Accessibility problems not listed in a component's known limitations.
- Documentation that contradicts what the catalogue actually returns.