We want everyone to have a great experience with ColorScripts-Enhanced. This document explains how to request help and what to expect from the maintainers.
| Scenario | Recommended Channel | Notes |
|---|---|---|
| Bug reports or regressions | GitHub Issues | Include reproduction steps, PowerShell version ($PSVersionTable), terminal, and screenshots when possible. |
| Feature requests | Feature Request template | Describe the problem, proposed solution, and potential alternatives. |
| Security vulnerabilities | Follow the Security Policy | Use private advisories or email the maintainer—do not open public issues. |
| Questions, setup help, or feedback | Issue tracker using the question label | We currently do not run GitHub Discussions; issues tagged question are welcome. |
| ANSI artwork conversions or script contributions | Open a draft PR or join an issue | Share previews or attach ANSI files; the maintainer can help convert or split files. |
- Initial response: Within 3 business days
- Follow-up on open issues: Weekly while active
- Security reports: As outlined in the Security Policy
- Review the Documentation index before filing a new issue.
- Search existing issues to avoid duplicates.
- Provide as much context as possible (operating system, PowerShell version, terminal, reproduction steps, and logs if relevant).
- Be respectful—our Code of Conduct applies to all support interactions.
Maintainers may not be able to provide support for:
- Custom ANSI art generation that is unrelated to the module
- Terminal emulator configuration outside of Nerd Font setup guidelines
- Issues caused by third-party forks or modified distributions
- Deprecated PowerShell versions (earlier than 5.1) or unsupported platforms
Please do not open public issues for potential vulnerabilities. Instead, follow the Security Policy to reach the maintainer privately.
Commercial support is not currently offered. If your organization requires custom terms or SLAs, open an issue to discuss options.