> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support and community

> Where to ask questions, report bugs, disclose security issues, and follow releases.

## Get help

| Channel | Use for |
| - | - |
| [Discord](https://discord.gg/JXG98xA6FH) | Questions, deployment advice, and discussion with other operators. |
| [GitHub issues](https://github.com/molesignal/molesignal/issues) | Bug reports and feature requests. |
| [support@molesignal.com](mailto:support@molesignal.com) | Questions that do not fit a public channel. |
| [GitHub releases](https://github.com/molesignal/molesignal/releases) | Release notes. The [Changelog](https://docs.molesignal.com/en-US/changelog.md) page shows the same list. |

Check [Troubleshooting](https://docs.molesignal.com/en-US/troubleshooting.md), [Known limitations](https://docs.molesignal.com/en-US/limitations.md), and the [FAQ](https://docs.molesignal.com/en-US/faq.md) first. They cover the most common problems.

## Report a bug

A report that includes these details is easier to reproduce:

* The version from `molesignal --version`, and the commit from `GET /api/v1/version`.
* The deployment type: Docker Compose, binary, or Kubernetes, and the roles that run.
* The relevant part of the configuration, with secrets removed.
* The log lines around the failure.
* The steps that trigger the problem, the expected result, and the actual result.

Never paste tokens, passwords, `MS_CIPHER_KEY`, or database connection strings into a public issue.

## Report a security vulnerability

Do not open a public issue for a vulnerability. Use one of the private channels:

* [GitHub private vulnerability reporting](https://github.com/molesignal/molesignal/security/advisories/new).
* [security@molesignal.com](mailto:security@molesignal.com). A PGP key is available on request.

Include a short description of the impact, a minimal reproduction, the version or commit that was tested, and a suggested severity.

The maintainers acknowledge a report within 3 business days and triage it within 7 business days. A fix or a mitigation plan for a high or critical issue follows within 30 days. Disclosure is coordinated, and reporters are credited in the release notes unless they ask to stay anonymous.

While MoleSignal is pre-1.0, security fixes go to the `main` branch and the latest tagged release. The `alpha` and `beta` channels receive forward fixes only.

## Contribute

MoleSignal is open source under the Apache License 2.0. The source, the contribution guide, and the issue tracker are in the [GitHub repository](https://github.com/molesignal/molesignal).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.