martinkalema/horizontal-scaling-convex
Grade a repo

0

/ 100

GradeB

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.

Documentation72
Engineering85
Health94
Rust14Othertoday

Documentation

72

README12pt50

README is present.

Contributing guide5pt61

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.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

85

Issue and PR templates6pt0

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.

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (crates/application/src/tests).

CI/CD14pt100

CI is configured (npm-packages/convex/.github/workflows/test-and-lint.yml).

Linting and formatting5pt100

Rust linting configured (.prettierrc.js).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 3
    Forks
  • 3
    Releaseslatest 18d ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 14
    Watchers

Responsiveness

  • 7d 7h
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files25 root entries
  • .cargo
  • .config
  • crates
    Good: Test files detected (crates/application/src/tests).
  • demo
    Issue: Build artifacts or local files may be committed (demo/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • npm-packages
    Good: CI is configured (npm-packages/convex/.github/workflows/test-and-lint.yml).
  • scripts
  • self-hosted
    Good: Environment pinned via self-hosted/docker/docker-compose.yml.
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • .nvmrc.22
  • .prettierignore
  • .prettierrc.js
    Good: Rust linting configured (.prettierrc.js).
  • BUILD.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CONTRIBUTING.md
    Issue: 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.md
    Good: 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.md
    Good: Licensed under Other.
  • README.md
  • rust-toolchain
  • rustfmt.toml