0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
A next-generation Scala framework for building scalable, correct, and efficient HTTP clients and servers
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
73
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
69
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
CI is configured (.github/workflows/ci.yml).
Test files detected (sbt-zio-http-grpc-tests/src/test).
Lockfile present (website/yarn.lock). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (docs/package.json).
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)
- 491Forks
- 65Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 867Watchers
Responsiveness
- 2dMedian issue response
- 2hMedian PR merge time
- 49Open issues
Repository files47 root entries
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- docsGood: Dependency manifest found (docs/package.json).
- profiling
- project
- sbt-zio-http-grpc
- sbt-zio-http-grpc-testsGood: Test files detected (sbt-zio-http-grpc-tests/src/test).
- websiteGood: Lockfile present (website/yarn.lock). Installs are reproducible.
- zio-http
- zio-http-benchmarks
- zio-http-cli
- zio-http-datastar-sdk
- zio-http-docs
- zio-http-example
- zio-http-example-basic-auth
- zio-http-example-cookie-auth
- zio-http-example-datastar-chat
- zio-http-example-digest-auth
- zio-http-example-jwt-bearer-refresh-token-auth
- zio-http-example-jwt-bearer-token-auth
- zio-http-example-oauth-bearer-token-auth
- zio-http-example-opaque-bearer-token-auth
- zio-http-example-testing
- zio-http-example-webauthn
- zio-http-gen
- zio-http-htmx
- zio-http-metrics
- zio-http-stomp
- zio-http-testkit
- zio-http-tools
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .sbtopts
- .scalafix.conf
- .scalafmt.conf
- aliases.sbt
- benchmark-zio-http.sh
- build.sbt
- build.sh
- context7.json
- default.nix
- global.sbt
- LICENSEGood: Licensed under Apache-2.0.
- netlify.toml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- renovate.json
- thanks.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/zio/zio-http)