slatedb/slatedb
Grade a repo

87

/ 100

GradeB

Well engineered. The main gaps are setup instructions and CI.

Top 18% of 5,156 graded repos

A cloud native embedded storage engine built on object storage.

Documentation79
Engineering87
Health100
Rust3,548Apache-2.024d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

79

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt66

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.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

87

CI/CD14pt68

CI is configured (.github/workflows/java.yaml).

Reproducibility6pt70

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

Tests18pt100

Test files detected (bindings/go/uniffi/admin_run_test.go).

Linting and formatting5pt100

Rust linting configured (rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 40 / 141
    Commits (30d / 90d)
  • 317
    Forks
  • 34
    Releaseslatest 1y ago

Community

  • 87% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 3,548
    Watchers

Responsiveness

  • 2d 9h
    Median issue response
  • 19h
    Median PR merge time
  • 213
    Open issues
Repository files32 root entries
  • .agents
  • .config
  • .github
    Good: CI is configured (.github/workflows/java.yaml).
    Good: Issue or PR templates present.
  • bindings
    Good: Test files detected (bindings/go/uniffi/admin_run_test.go).
  • examples
  • rfcs
  • schemas
  • scripts
  • slatedb
  • slatedb-bencher
  • slatedb-cli
  • slatedb-common
  • slatedb-dst
  • slatedb-txn-obj
  • specs
  • website
  • .gitignore
    Good: .gitignore present.
  • .typos.toml
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • CLEAN_SLATE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README.md
    Good: 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.
  • RELEASE.md
  • rust-toolchain.toml
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml).
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/slatedb/slatedb)](https://www.repo-grade.com/report/slatedb/slatedb)

More graded Rust repos