Contact ViteHub

ViteHub is maintained as an open-source project. It does not operate a sales desk, paid support queue, or hosted customer account system. Choose a channel based on what you need so maintainers and contributors receive enough context to act without moving sensitive information into a public thread.

Questions and implementation help

Use the ViteHub Discord community for implementation questions, design discussion, and help choosing between Server Primitives and Agents. Include the installed ViteHub package version, the host or framework, the expected behavior, and a minimal example when possible. Remove tokens, personal data, private repository content, and provider credentials before posting.

Bugs and documentation

Open a GitHub issue for a reproducible bug or a documentation gap. Search existing issues first, then describe the observed behavior, the expected contract, and the smallest command or repository that reproduces it. Documentation fixes can also be proposed as pull requests against the public repository.

Security reports

Do not publish a suspected vulnerability in Discord or a public issue. Use a private GitHub security advisory so the report, proof, and remediation discussion remain private until maintainers can assess the impact. Include affected versions and a safe reproduction. Do not include credentials or data taken from systems you do not own or have permission to test.

ViteHub does not publish a support phone number or postal office. If the project adopts a legal entity, mailing address, or dedicated support email, this page and the site's structured identity data should be updated together.