- Srinivas Vaddi (@vaddisrinivas) — Creator & Lead Maintainer
- Small changes (bug fixes, docs, typos): Merged directly by maintainer after CI passes.
- Features (new tools, APIs, config options): Discussed in a GitHub Issue before implementation; maintainer approves.
- Major changes (breaking APIs, architecture rewrites, new major version): RFC label on a GitHub Discussion, community feedback period of at least 7 days, maintainer final decision.
- Patch (
2.0.x): Critical fixes, released as needed. - Minor (
2.x.0): New features, released when ready. - Major (
x.0.0): Breaking changes, planned with deprecation notices in the prior minor release.
All releases follow Semantic Versioning.
- All changes go through pull requests (no direct pushes to
main). - PRs require passing CI (tests, lint, type check) before merge.
- Maintainer reviews and merges; community reviewers welcome.
- Typical review turnaround: 1-3 business days.
See SECURITY.md for vulnerability reporting and response SLAs.
All contributions are licensed under the project's MIT License. By submitting a pull request, you agree that your contribution is licensed under the same terms.
As the community grows, we welcome co-maintainers. Path to co-maintainership:
- 5+ merged pull requests demonstrating code quality and project understanding
- Active participation in issue triage or code review
- Discussion with the lead maintainer
- Added to CODEOWNERS