Varendo

Contribute to Varendo

Find the canonical contributor guides, report defects, and use the right private channel for sensitive reports.

Documentation, runnable examples, defect reports, and focused code changes are welcome. These public docs are the product reference; contributor setup and repository rules live alongside the source.

Make a contribution

  1. Read CONTRIBUTING.md for the pinned toolchain, local setup, commit sign-off, and pull request flow.
  2. Read AGENTS.md for package boundaries, code conventions, ownership, and required verification.
  3. Use the technical documentation index to find architecture and maintenance guidance. Edit canonical Markdown or generator sources rather than generated artifacts.
  4. Open a focused pull request with a reproducible example, updated docs, and fresh output from the checks relevant to the change.

Report a defect or ask for help

Follow SUPPORT.md, then open a GitHub issue. Include exact package and environment versions, expected and observed behavior, and a small reproduction using synthetic data. Remove credentials and customer records from logs, screenshots, and exported projects.

Conduct reports

Participation follows the Code of Conduct. Use GitHub's Report abuse control on the relevant content or profile; see GitHub's reporting instructions. GitHub handles those reports under its own policies. This is not a private project moderation inbox, and the project makes no response-time promise.

Security reports

Follow SECURITY.md and submit a private vulnerability report. Keep exploit details and sensitive evidence out of public issues. Include the version, entry point, affected boundary, and a minimal reproduction. No monitored security email address or response-time SLA is published.