Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 1.57 KB

File metadata and controls

44 lines (33 loc) · 1.57 KB

Support

Maniflight is maintained on a best-effort basis. The following routes keep questions actionable and security reports private.

Choose a channel

  • Unexpected behavior: open a bug report with a minimal repository fixture or sanitized reproduction.
  • How-to question: use the support-question issue form and explain what you tried.
  • New capability: open a feature request that describes the user problem, not only a proposed implementation.
  • New or changed rule: use the rule-proposal issue form.
  • Security concern: follow SECURITY.md and do not open a public issue.

Before opening an issue, search existing issues and review docs/RULES.md, docs/SCORING.md, and the roadmap.

Include enough context

For scan or report problems, include:

  • the Maniflight version or commit;
  • Node.js version and operating system;
  • the exact command, with tokens and private paths removed;
  • the smallest repository structure that reproduces the problem;
  • expected and actual rule outcomes; and
  • relevant console output or a sanitized JSON report.

Never post tokens, credentials, private source, or an unredacted private repository report.

Scope

Community support covers the documented CLI, GitHub Action, rule behavior, configuration, and generated report. It does not include private consulting, repository certification, legal or compliance advice, or guaranteed response times.

Maniflight findings are diagnostic signals, not a substitute for code review, security testing, or production monitoring.