LET’S MAKE THE NEXT STEP CLEAR.

Start a conversation.Bring the context.

For project questions, collaboration and technical feedback, use the maintainer’s GitHub profile or the project issue tracker.

01 /

Project questions

Include the goal, relevant workflow, deployment environment and the outcome you need. Keep credentials and private client data out of public messages.

  • Describe the problem and expected behavior
  • Include reproducible steps for a bug
  • Use private reporting for security details
02 /

Security reports

Use the repository’s private vulnerability reporting channel for sensitive findings. Public issues are appropriate for general documentation and non-sensitive defects.

  • Read the security policy first
  • Provide a minimal reproducible report
  • Do not publish access tokens or personal data
03 /

Support expectations

This independently maintained project has no contracted response-time SLA. Commercial delivery and operational support are agreed separately.

  • Public issues: general support
  • Private reports: vulnerabilities
  • No message is sent by this website
Keep exploringExplore the roadmap
MAKE ROOM FOR WHAT’S NEXT

Great work startswith together.

Step into the workspace