Security

Last updated: 28 October 2026

If you think you have found a security issue in Euthyne, please tell us. We read every report and we are grateful for your help.

How to report

Email hello@euthyne.com, in English or French, with "Security" in the subject. Include what you found, where, the steps to reproduce it and the impact you expect. Please do not include other people's personal data beyond what is needed to show the issue.

Our machine-readable contact details are in /.well-known/security.txt.

Scope

  • euthyne.com and its subdomains
  • software we publish, including the euthyne command-line tool and the Euthyne integrations for GitHub and GitLab
  • receipt signing, the transparency log and the verification of receipts

Out of scope:

  • services run by others, such as GitHub, GitLab, Hetzner, Resend or Porkbun. Report those to their owners.
  • denial of service, load testing, spam, social engineering and physical attacks
  • reports from automated scanners without a demonstrated impact

Rules

  • Use only accounts and organizations you own or are allowed to test.
  • Do not access, change or delete other people's data. If you reach it by accident, stop, do not keep it, and tell us.
  • Do not degrade the service for others.
  • Give us reasonable time to fix the issue before you disclose it publicly. We suggest 90 days, and we are happy to agree on a date with you.

Verifying a CLI release

Releases of the euthyne command-line tool on GitHub that include a checksums.txt.sigstore.json file are signed with Sigstore keyless signing by our release workflow. The signature is recorded in the public Sigstore transparency log. Download checksums.txt, its bundle and your archive into one folder, then check the signature with cosign and the archive against the checksums:

cosign verify-blob \
  --bundle checksums.txt.sigstore.json \
  --certificate-identity https://github.com/euthyne-labs/euthyne/.github/workflows/release.yml@refs/heads/main \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  checksums.txt
sha256sum --ignore-missing -c checksums.txt

Both commands must succeed. A signature from any other identity or issuer means the file did not come from our build. On macOS without sha256sum, use shasum -a 256 --ignore-missing -c checksums.txt.

Good faith

If you follow these rules in good faith, we will not take legal action against you, or ask anyone else to, for your research. We cannot give that assurance on behalf of third parties, and it does not cover actions that harm users or their data.

What we do with your report

  • We acknowledge it within 5 business days.
  • We investigate, keep you informed, and tell you when the issue is fixed.
  • If personal data was affected, we inform the customers concerned and, where the law requires it, the CNIL.
  • With your permission, we credit you once the fix is out.

We do not run a paid bug bounty.