Contributing to Streamdal

We're updating our documentation, so the presented info might not be the most recent.

Streamdal is an open-source project using the Apache License, Version 2.0. Feature proposals and general contributions are cherished and highly encouraged! Most of the components can be found in the monorepo.

Here is the repo structure:

# β”œβ”€β”€ apps
# β”‚   β”œβ”€β”€ cli                <--- CLI UI 
# β”‚   β”œβ”€β”€ console            <--- Web-based UI
# β”‚   β”œβ”€β”€ docs               <--- 
# β”‚   β”œβ”€β”€ server             <--- Server component
# β”‚   └── ...
# β”Œβ”€β”€ assets                 <--- Static assets 
# β”‚   β”œβ”€β”€ img
# β”‚   └── ...
# β”œβ”€β”€ docs
# β”‚   β”œβ”€β”€ install             <--- different methods of deploying/installing Streamdal
# β”‚   β”œβ”€β”€ instrument          <--- instrumenting Streamdal in various languages
# |   └── ...
# β”œβ”€β”€ libs
# β”‚   β”œβ”€β”€ protos             <--- Common protobuf schemas
# β”‚   β”œβ”€β”€ wasm-detective     <--- Wasm lib used for data parsing and validation 
# β”‚   β”œβ”€β”€ wasm-transformer   <--- Wasm lib used for data transformation
# β”‚   β”œβ”€β”€ wasm               <--- Wasm funcs used in pipeline steps
# β”‚   └── ...
# β”œβ”€β”€ scripts                   
# β”‚   β”œβ”€β”€ install
# β”‚   β”‚	  └──     <--- Install script for installing Streamdal
# β”‚   └── ...
# β”œβ”€β”€ sdks                   
# β”‚   β”œβ”€β”€ go                 <--- Golang SDK
# β”‚   β”œβ”€β”€ node               <--- Node SDK
# β”‚   β”œβ”€β”€ python             <--- Python SDK
# β”‚   β”œβ”€β”€ ruby               <--- Ruby SDK
# β”‚   └── ...
# β”œβ”€β”€ LICENSE
# β”œβ”€β”€ Makefile               <--- Makefile with common tasks; run `make help` for more info
# └──

General Guidelines & References


New to open source?

Be sure to check for some good first issues periodically.

Here are some references and simple guidelines you should go over to help ensure contributions go smoothly:

  1. The Code of Conduct

  2. Streamdal technology stack:

    • Wasm

    • Protobuf

    • gRPC + gRPC-web

    • Rust

    • Go

    • React

    • Flowbite

    • Deno

    • Redis

    • Envoy

    • …and many more open source libraries and tools

      Check out our open source page to learn more about what other technologies are used with Streamdal.

  3. The Streamdal manifesto - this should help you gauge where our mindset is focused when it comes to future development

  4. Public roadmap


Getting support:
We primarily provide support for issues through the main monorepo. To bring more visibility to your issue, or for quick questions, ask in the community discord.

Adding an Issue

Before adding issues, you should:

  1. Be familiar with the core components
  2. Search for existing issues

Issues for components outside of the monorepo, like language-specific shims or client SDKs, should be made in those specific repositories. You can find these listed above, on the monorepo, or by searching through the Streamdal public repositories.


We utilize conventional commits to structure issues.

You should format the name of your issue as close as possible to the following examples:

  • feat: <description> β€” The type feat introduces a new feature to the codebase. Use this for proposals as well. (This can be/is sometimes marked as chore)
  • fix: <description> β€” You’ve found a bug with the code and want to report it, or create an issue to track the bug.
  • discussion: <description> β€” You have something on your mind, which requires input from others in a discussion. This could pertain to niche deployments, edge use cases not well documented, or anything else that might be relevant. Use this for questions as well.

Component Versions

Issues should always list (where applicable) the version of everything you are using.

If you’re using docker-compose, you can check the docker-compose.yml for versions, else you can do the following for each component:

    • Server:

      You can curl the version from the server REST API endpoint by adding /version:

    curl http://streamdal.server:8081/version

    • SDK:

      This is language specific. You can find this in /releases of the URL (Replace $lang with the language you are using):$lang

    Note: Since moving to the monorepo, the releases have changed. More info will be added here about listing SDK version soon!

    • Console UI:

      cat the version.ts file located in the root directory where the Console UI is running. It is also visually indicated at the bottom left corner of the UI:

    Example of Streamdal console version
  1. Include a thorough description of what your code does inside the PR. Preferably, include a screenshot if it applies.

If you feel it necessary, or for some reason an important issue is going unnoticed, you are also permitted to cross-post issues to the community for greater visibility.

Pull Requests

All contributions come through pull requests. Follow these guidelines when contributing code or docs to Streamdal:

  1. Make sure there’s an issue (fix or feat) raised, which sets the expectations for the contribution you are about to make
  2. Clone relevant repo and create a new branch
  3. Create your change β€” Code changes require tests, and make sure to run linters to check and format the code
  4. Update relevant documentation for the change - Please check the doc’s README for helpful information on contributing to docs
  5. Commit with DCO sign-off and open a PR
  6. Wait for the CI process to finish and make sure all checks are green. A maintainer of the project will be assigned, and you can expect a review within a few days

Any contribution that you make to Streamdal repositories will be under the Apache 2.0 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise, any 
Contribution intentionally submitted for inclusion in the Work by You to the 
Licensor shall be under the terms and conditions of this License, without any 
additional terms or conditions. Notwithstanding the above, nothing herein shall 
supersede or modify the terms of any separate license agreement you may have 
executed with the Licensor regarding such Contributions.


A good way to communicate before investing too much time is to create a β€œWork-in-progress” PR and share it with your reviewers. The standard way of doing this is to add a β€œ[WIP]” prefix in your PR’s title and assign the do-not-merge label. This will let people looking at your PR know that it is not well baked yet.

Developer Certificate of Origin: Signing your work

Every commit needs to be signed

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

    (a) The contribution was created in whole or in part by me and I have the 
    right to submit it under the open source license indicated in the file; or

    (b) The contribution is based upon previous work that, to the best of my 
    knowledge, is covered under an appropriate open source license and I have 
    the right under that license to submit that work with modifications, 
    whether created in whole or in part by me, under the same open source 
    license (unless I am permitted to submit under a different license), as 
    indicated in the file; or

    (c) The contribution was provided directly to me by some other person who 
    certified (a), (b) or (c) and I have not modified it.

    (d) I understand and agree that this project and the contribution are 
    public and that a record of the contribution (including all personal 
    information I submit with it, including my sign-off) is maintained 
    indefinitely and may be redistributed consistent with this project or the 
    open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

<This is my commit message>

Signed-off-by: Random Dev <[email protected]>

Git even has a -s cli flag to append this automatically to your commit message:

git commit -s -m 'This is my commit message'

Each PR is checked whether or not the commits contain a valid Signed-off-by line.

Unsigned commits

Forget to sign the commit? No problem! Just amend your changes, sign them, and force push them:

git checkout <branch-name>
git commit --amend --no-edit --signoff
git push --force-with-lease <remote-name> <branch-name>

Code of Conduct

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind
  • Trolling, insulting or derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as a physical or email address, without their explicit permission
  • Other conduct that could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.


This Code of Conduct applies within all community spaces and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.


Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement:

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident. If you feel that judgments were inappropriately applied to you or others in the community, feel free to reach out to the founders directly.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

  1. Correction
  2. Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

    Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

  3. Warning

  4. Community Impact: A violation through a single incident or series of actions.

    Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

  5. Temporary Ban

  6. Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

    Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

  7. Permanent Ban

  8. Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

    Consequence: A permanent ban from any sort of public interaction within the community.


This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at

Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at

Translations are available at