Skip to content

Security: TurboWarp/packager

SECURITY.md

Reporting a vulnerability

Report security vulnerabilities to [email protected] instead of the public issue tracker.

If you don't get a response within 48 hours, post a GitHub issue asking for an update. It may have been flagged as spam. (do not post any details publicly, just ask if your email was seen)

Bug Bounty

We don't have a large budget, but we take security very seriously. I will pay out a bug bounty starting at $20 USD for high severity bugs like these (non-comprehensive):

  • XSS in places such as the compiler or any extension in the official extension gallery (including unlisted ones)
  • Sandbox escape in the desktop app (such as arbitrary file read/write) assuming that XSS has already been achieved (so running any code in an extension or developer tools is fair game)
  • Code execution/memory corruption/etc. on any of our backend services.

These types of bugs may be eligible for a reduced bounty (non-comprehensive):

  • Scratch.canFetch(), Scratch.canOpenWindow(), etc. bypass in extensions in the official extension gallery (including unlisted ones)
  • Security bugs in deprecated or low-priority subprojects such as the TurboWarp Desktop legacy builds for old operating systems or old experimental branches.
  • Open redirect on any TurboWarp website

Guidelines:

  • Participation in this program is contigent upon you acting in good faith.
  • No bounties for bugs you created yourself.
  • The bug needs to work on the latest version in git at the time of reporting.
  • The bounty can be paid in almost any format you desire or be donated to a charity of your choice.
  • The decision about whether you get a bounty and its size is ultimately up to me.

Examples of bugs that might not be eligible for a bounty:

  • Bugs in upstream projects such as Scratch, Scratch Addons, Electron, Chromium, etc. Please report these to the appropriate upstreams.
  • Missing "security headers" such as X-Frame-Options or Content-Security-Policy without demonstrated impact.
  • Self-XSS.
  • Vulnerable code that is in a TurboWarp repository but does not actually run anywhere in TurboWarp, for example, extensions that have compatibility code that doesn't run in TurboWarp.

There aren’t any published security advisories