How to reach us
Email security@crela.io. This address is monitored for security reports only. For anything else, use contact@crela.io.
Please include enough detail for us to reproduce the issue: the affected URL or component, the steps you took, and what you observed. A short proof of concept helps more than a scanner report. Screenshots and logs are welcome. Write in English or German, whichever is easier for you.
If the finding is sensitive, encrypt it with our OpenPGP key at /.well-known/pgp-key.txt. The same key signs our security.txt.
What we promise
- We acknowledge your report within 72 hours. If you have not heard back by then, assume it did not arrive and send a reminder.
- We give you an initial assessment within 7 business days, including whether we consider it a vulnerability and roughly when we expect a fix.
- We keep you updated while we work on it, and we tell you when it is fixed.
- We credit you by name when the fix ships, if you want that. Tell us how you would like to be named, or that you prefer to stay anonymous.
Crela is run by a small team. These are the timelines we can actually keep, which is why they are not shorter.
Safe harbour
If you follow this policy in good faith, we will not pursue legal action against you and will not report you to law enforcement. We consider your research authorised access for the purposes of computer misuse laws, and we will say so if a third party claims otherwise.
This protection covers you as long as you stay within the scope below, stop as soon as you have confirmed a finding, and give us a reasonable chance to fix it before going public. We ask for 90 days. If you believe users are at immediate risk, say so and we will move faster.
In scope
- The website and web application at crela.io, including its API.
- The Crela launcher, its update mechanism, and its licence handling.
- The review pipeline itself, in particular ways to make a build pass review that should not pass.
- Our published packages on npm under the crela scope.
Out of scope
The following are not in scope, and reports about them will be closed without assessment.
- Software published by creators on Crela. We review what creators submit, but we do not write it and we cannot patch it. If you find a vulnerability in a tool sold here, report it to its creator. Tell us as well if you believe the tool is malicious rather than merely flawed, and we will act on the listing.
- Findings that only show a missing hardening header, a weak cipher suite, or a similar configuration preference, without a demonstrated impact.
- Reports produced solely by an automated scanner, with no analysis of whether the finding is exploitable here.
- Issues in third party services we use but do not operate. Report those to the provider.
- Social engineering, phishing, or physical access attempts against us, our users, or our creators.
Rules while testing
Test against your own account and your own data. Concretely, please do not:
- Run denial of service attacks, load tests, or anything else that degrades the service for others.
- Access, modify, or download data belonging to another user or creator. If you can prove access, stop there and tell us what you could reach.
- Use social engineering or phishing against anyone.
- Leave persistent changes behind. Remove any test accounts, uploads, or listings you created.
No bounty
We do not operate a paid vulnerability programme, and we would rather say that plainly than imply a payment we will not make. What you get is a fast, honest response, credit for the finding, and our thanks.
Machine readable version
The same contact details are published at /.well-known/security.txt, following RFC 9116 and signed with OpenPGP.


