Community
StreetJS is open source (MIT) and contributor-driven. Here's how to get involved.
Ways to participate
| Ask & discuss | GitHub Discussions |
| Report issues | GitHub Issues |
| Contribute code/docs | Contributing guide · good first issues |
| Propose changes | RFC process |
| Report a vulnerability | Security policy |
Contributor path
StreetJS uses an explicit ladder from first-time contributor to maintainer — see the contributor path:
first-time → recurring contributor → reviewer → maintainer → Steering Committee
The highest-leverage first contributions are tutorials, examples, and plugins (the signed-plugin model makes a new plugin a clean, self-contained PR — see the Plugin Author Guide).
Governance & RFCs
StreetJS is governed by a documented model (GOVERNANCE.md) with a Steering
Committee and a public RFC process for substantial changes. Two RFCs are
accepted to date (ORM relations; the full-stack expansion). New significant work
starts as an RFC PR.
Maintainers & bus-factor
The project is candid that growing to 2+ active maintainers is the top priority (see the Adoption & Go-To-Market Roadmap). If you’d like to help maintain a subsystem, open a Discussion — the release pipeline is fully automated and signed, so onboarding a co-maintainer is low-risk.
Code of Conduct
All participation is governed by the project Code of Conduct.