Projektor
Contact / route the signal

Send it to the right channel.

Projektor is an open-source, pre-1.0 project, not a staffed support service. There is no ticket portal or guaranteed response time; the routes below go directly to the repository or maintainer.

Contact matrix

Bugs stay searchable. Vulnerabilities stay private.

Public / reproducible01 / 04

Something broke

Open a bug report with the browser, operating system, GPU when known, steps to reproduce, and a screenshot or recording. A safe project link can make visual bugs much easier to inspect.

File a bug report ↗
Public / product idea02 / 04

A workflow is missing

Use the feature template to describe the job, the result you want, and whether the browser can expose the required device or protocol. Concrete use cases are more useful than a feature name alone.

Request a feature ↗
Private / vulnerability03 / 04

You found a security issue

Do not open a public issue. Send a private GitHub Security Advisory with the impact and reproduction steps, or email the maintainer if an advisory is not practical.

Open a private advisory ↗
Private / direct note04 / 04

You need the maintainer

For a private project question that is not better handled in a public issue, write directly. Security reports are still best sent through the advisory channel above.

vedanthbora@gmail.com
Security / private channel

Never disclose a vulnerability in a public issue.

Shared project links and .projektor files are untrusted input; runtime GLSL, camera permissions, and same-origin output sync also deserve careful handling. Include the impact and smallest safe reproduction in a private advisory.

Before filing

Make a visual problem reproducible.

  1. 01

    Reduce the problem to the fewest actions you can.

  2. 02

    Name the browser, operating system, and GPU when known.

  3. 03

    Say whether it happened in the editor or the Go Live output.

  4. 04

    Attach a screenshot or short recording for visual failures.

Contributions

A pull request is also a contact channel.

The contribution guide explains the engine boundary, validation rules, and CI gates. Start with an issue when the design or scope needs discussion first.

  • 01Geometry, WebGL, and render-path fixes
  • 02New media providers or shader examples
  • 03Editor accessibility and interaction polish
  • 04Documentation, tests, and reproducible bug reports
No issue to file?

Open the editor and move some light.

Open the editor →