Get help and share feedback
Ask questions, report bugs, and suggest features with enough context for contributors to help.
On this page
Questions and feature ideas are welcome. Start with the quickstart, supported systems, or troubleshooting. Desktop users can follow the desktop guide.
Open an issue
Search existing issues first, then choose a form:
Support is provided by contributors on a best-effort basis, without a guaranteed response time. See the repository’s support policy.
Help us reproduce the problem
Include:
debark version --json; for the GUI, also include its version from About.- Builder OS and architecture, target release and architecture, and snapshot or baseline choice.
- The command or UI steps, backend, expected behavior, actual result, and exit code.
- A small package list or synthetic fixture, relevant logs, and container runtime details.
- The affected page URL and incorrect text for website or documentation problems.
Review logs and attachments before posting. Snapshots, URLs, and bundle metadata can
contain private infrastructure details or credentials. --redact removes selected fields,
but does not fully anonymize a snapshot. Never post a private signing key.
Private reports and contact
Report vulnerabilities through GitHub private vulnerability reporting. Follow SECURITY.md, including its fallback if private reporting is unavailable. Use the reporting route in the Code of Conduct for conduct concerns.
For general contact, reach Iman Kamyabi at imankamyabi@pm.me. Debark is maintained at InferOps LLC; find our main website at inferops.com. Public usage questions and feature requests are best shared in issues so other users can find the answers.