0
/ 100
Strong early engineering with some momentum.
Experimental Convex backend fork aiming to scale Convex horizontally while preserving its core semantics: reactive subscriptions, serializable transactions, and consistent snapshots.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
72
README is present.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
Licensed under Other.
Engineering
85
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/application/src/tests).
CI is configured (npm-packages/convex/.github/workflows/test-and-lint.yml).
Rust linting configured (.prettierrc.js).
Project health
94
.gitignore present.
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 3Forks
- 3Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 14Watchers
Responsiveness
- 7d 7hMedian issue response
- <1hMedian PR merge time
- 13Open issues
Repository files25 root entries
- .cargo
- .config
- cratesGood: Test files detected (crates/application/src/tests).
- demoIssue: Build artifacts or local files may be committed (demo/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- docs
- npm-packagesGood: CI is configured (npm-packages/convex/.github/workflows/test-and-lint.yml).
- scripts
- self-hostedGood: Environment pinned via self-hosted/docker/docker-compose.yml.
- .dockerignore
- .gitignoreGood: .gitignore present.
- .nvmrc
- .nvmrc.22
- .prettierignore
- .prettierrc.jsGood: Rust linting configured (.prettierrc.js).
- BUILD.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- CONVEX-README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- dprint.json
- Justfile
- LICENSE.mdGood: Licensed under Other.
- README.md
- rust-toolchain
- rustfmt.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/martinkalema/horizontal-scaling-convex)