Support

Lumen is pre-release and has no service-level support commitment. Support reports are most useful when they identify one reproducible boundary and omit data that does not belong in a public project space.

Select a channel

• Use GitHub issues for reproducible product defects and narrowly scoped feature proposals.
• Use GitHub Discussions for usage questions when Discussions is enabled.
• Use private security reporting for vulnerabilities.
• Use the private path in the code of conduct for conduct concerns.

Do not move a vulnerability or sensitive conduct report into a public issue merely because a public channel responds faster.

Include useful evidence

State the Lumen commit, operating system and architecture, pinned Node/Python/package-manager versions, browser when relevant, deployment profile, expected behavior, observed behavior, and the smallest reproduction. Include the exact command and exit result, the first useful error, and sanitized logs. For interface defects, name the route, viewport, input method, appearance, and whether the console or network recorded a failure.

Before opening a report, check the current documentation and existing issues, then reproduce from a clean supported setup when practical. Do not erase the original state simply to obtain a clean run; preserve the evidence and explain any recovery step you tried.

Protect project and personal data

Never post credentials, bearer tokens, private research, proprietary datasets, personal information, provider-administration output, or unredacted environment files. Replace sensitive values with stable labels that still show where values differ. If safe sanitization is not possible, ask privately which minimal evidence is needed.

Maintainers may request a smaller reproduction, move a usage question to the appropriate channel, or close work that cannot be reproduced on the supported pre-release branch. This page does not promise a response or resolution time.