Skip to content

Reporting security issues

A dedicated, monitored security reporting channel and disclosure process have not yet been established in this documentation. No acknowledgement time, response deadline, remediation deadline, bug bounty or safe-harbour commitment is offered here.

Requesting a suitable contact

To ask where a concern should be sent, use the existing Realworld company contact form with a short, non-sensitive summary and your preferred reply address. Ask for a suitable private route before providing technical detail. This is a general company enquiry route, not a verified security intake service or a commitment that a report will be triaged within a particular time.

For an initial request, identify only the affected public page or product, its visible version if available, and the broad category of concern. Do not put a working exploit, private evidence or suspected secret into the form.

Preparing a report

Once an appropriate private route has been confirmed, useful information includes:

  • The affected specification edition, software version or public URL.
  • The behaviour you expected and the behaviour you observed.
  • A minimal reproduction using synthetic data, where authorised and safe.
  • The potential impact, relevant conditions and whether the issue remains reproducible.
  • Your contact details and any constraints on sharing the report.

Never include private signing keys, access or refresh tokens, passwords, real credentials, borrower or client details, restricted reports or other people's personal information. Sanitise logs and screenshots before sharing them. If sensitive material was exposed, describe its category and location without copying its value.

Avoid public issue trackers, public comments or public attachments for unresolved vulnerability detail. For a non-sensitive specification ambiguity, a reference to the relevant page and a synthetic example is normally sufficient for the initial enquiry.

Scope and permission

This page does not authorise testing of a live system, including demonstration services, or access to another party's data. Agree the target, method, limits and reporting route with the system owner before conducting security testing. A third party's implementation remains subject to that operator's permissions and reporting arrangements.

A future reporting policy needs a named owner, a tested channel, an agreed handling process and a clear scope before it can make operational commitments. Until those are published, this page makes no promise about acknowledgement, investigation, disclosure timing or legal protection.

Security overview · Trust and responsibilities · Assurance and release