# Code of Conduct

## Our pledge

This project is maintained in a professional, technical tone. Everyone is welcome to
use it, report problems and propose changes, regardless of experience level, language,
country of origin or employer.

## Expected behaviour

- **Be specific.** Bug reports with input, command and output get solved; opinions without
  evidence usually do not.
- **Criticise the code, not the person.** "This regex drops the first line" is useful;
  "you clearly do not know Bash" is not.
- **Assume good faith on scope.** A maintainer may decline a feature that fits your
  workflow but not the tool's single purpose.
- **Keep threads on topic.** Unrelated promotion, politics and personal disputes belong
  elsewhere.

## Unacceptable behaviour

- Insults, harassment, discriminatory remarks, or sexualised language and imagery.
- Publishing someone's private information (address, phone, credentials, private
  correspondence) without permission.
- Deliberately submitting malicious code, backdoors, credential collectors or
  obfuscated payloads, including in "example" Markdown.
- Spam: repeated comments, irrelevant links, advertising.
- Pressing for unpaid private support after a "no".

## Scope

The rules apply to issues, pull requests, discussions, commit messages and any other
space where the project is discussed, including private messages sent in a project
context.

## Enforcement

Report a problem to the maintainer at **mid1977@gmail.com**. Reports are read within a
few days. Depending on severity, the response is one of:

1. a clarification request in the thread;
2. a warning, with the offending content removed or hidden;
3. a temporary block from the repository;
4. a permanent block and a report to the platform.

The maintainer recuses from decisions about reports involving themselves; in that case
the report goes to GitHub Support.

---

*Applies to all project spaces from 2026-10-19.*