Polished and well engineered. Punching above its star count.
SGLang Omni: High-Performance Multi-Stage Pipeline Framework for Omni Models
Documentation
73
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
98
Lockfile present (docs/requirements.txt). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/lint.yaml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
96
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 218Forks
- 1Releaseslatest 10d ago
Community
- —Community health
- —authors own >50% of commits
- 529Watchers
Responsiveness
- 20hMedian issue response
- <1hMedian PR merge time
- 208Open issues
Repository files19 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/lint.yaml).Good: Issue or PR templates present.
- benchmarksGood: Environment pinned via benchmarks/tts_serving/Dockerfile.
- docker
- docsGood: Lockfile present (docs/requirements.txt). Installs are reproducible.
- examples
- playground
- scripts
- sglang_omni
- sglang_omni_router
- testsGood: Test files detected (tests).
- .dockerignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .isort.cfg
- .pre-commit-config.yaml
- LICENSEGood: Licensed under Apache-2.0.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.