0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Toolkit for Scala Development
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (84).
See your top fixesTop 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
84
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under Apache-2.0.
Engineering
59
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/build.yml).
Test files detected (kyo-actor/shared/src/test).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 118Forks
- 26Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 782Watchers
Responsiveness
- 11d 4hMedian issue response
- 12hMedian PR merge time
- 26Open issues
Repository files68 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- kyo-actorGood: Test files detected (kyo-actor/shared/src/test).
- kyo-aeron
- kyo-bench
- kyo-browser
- kyo-caliban
- kyo-case-app
- kyo-cats
- kyo-combinators
- kyo-compat
- kyo-config
- kyo-core
- kyo-data
- kyo-direct
- kyo-doctest
- kyo-examples
- kyo-ffi
- kyo-flow
- kyo-http
- kyo-jsonrpc
- kyo-jsonrpc-http
- kyo-kernel
- kyo-logging-jpl
- kyo-logging-slf4j
- kyo-offheap
- kyo-parse
- kyo-pod
- kyo-prelude
- kyo-reactive-streams
- kyo-scheduler
- kyo-scheduler-cats
- kyo-scheduler-finagle
- kyo-scheduler-pekko
- kyo-scheduler-zio
- kyo-schema
- kyo-slack
- kyo-stats-otlp
- kyo-stats-registry
- kyo-stm
- kyo-tasty
- kyo-test
- kyo-ui
- kyo-website
- kyo-website-bundle
- kyo-zio
- kyo-zio-test
- project
- scripts
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .jvmopts
- .readthedocs.yaml
- .scalafmt.conf
- AGENTS.md
- build.sbt
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- kyo-logo.pdf
- kyo.png
- kyo.svg
- LICENSE.txtGood: Licensed under Apache-2.0.
- MANIFESTO.md
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/getkyo/kyo)