Help

The projects published on VineLabs are open-source side work, maintained in my spare time. There is no SLA, no paid tier, and no service desk - but there is a real person reading every issue and email.

1. Where to ask

• Bugs and feature requests: open an issue on the project's repository at github.com/vinelabs-de. That is the canonical place; everyone benefits from the public discussion.
• Questions and discussions: GitHub Discussions on the relevant repo, where enabled.
• Email when GitHub is not appropriate: support@vinelabs.de for project help, info@vinelabs.de for general feedback.

Communication can be in English or German. Please do not send DMs on social platforms - I will not see them.

2. What to expect

These are open-source side projects, not a managed product. A few honest expectations:

• I usually respond within a few days, often sooner. Sometimes life gets in the way and it takes longer.
• I am not on call. There is no 24-hour response window except for confirmed security issues (see section 4).
• Some issues will be closed as "won't fix" if they fall outside the project's stated scope. The README is the source of truth on what each project tries to be.
• Pull requests with a clear bug fix or a documented feature are very welcome.

3. What to include in an issue or email

Fast, useful answers depend on a clear report. Please include:

• Project name and exact version (for example: vaultctl 0.5.2 or xrechnung-kit-core 3.1.0).
• How you installed it (binary, container image, Composer, source build).
• Runtime versions (PHP version including extensions, Go version, Node version, OS, etc.).
• What you expected to happen, and what happened instead.
• Reproduction steps. The smaller the better.
• Relevant logs and stack traces, with secrets redacted (replace tokens with ***).

For e-invoicing (xrechnung-kit) issues, please attach the input value object and the validator output. For vaultctl, please do not attach your encrypted vault file.

4. Security disclosure

Found a security issue? Please do not open a public issue. Email support@vinelabs.de with the subject prefix [security]. I will acknowledge within 24 hours, coordinate disclosure, and credit your report (or keep it anonymous on request).

Each repository ships a SECURITY.md with a PGP key and the canonical reporting flow. The default coordinated-disclosure window is 90 days, shortened in cases of active exploitation.

5. What is and is not covered

In scope for help on these channels:

• Bugs in the published packages and binaries.
• Documentation gaps and unclear error messages.
• Questions about how the project is meant to be used per its README and docs.
• Coordinated security disclosure as described above.

Not in scope:

• Forks where core security or cryptographic code has been modified - please upstream the fix instead so everyone benefits.
• Versions older than two minor releases behind the current stable.
• Glue code that is not part of the published packages (your specific deployment topology, your CI scripts, your custom adapters).
• Migrations of legacy systems and bespoke integration work.

6. No warranty - open-source licenses govern

The projects published on VineLabs are released under their respective open-source licenses (e.g. AGPL-3.0, MIT). The warranty disclaimer in each license file governs the relationship between you and the software. Nothing on this page modifies or extends those license terms, and nothing on this page constitutes a service agreement, support contract, or commercial undertaking.

If you are using one of these projects and run into trouble, the best thing to do is the same thing the rest of the community does: open an issue, share what you know, and if you can, contribute the fix.