slatedb/slatedb

0

/ 100

Documentation79
Engineering96
Health100
Rust3,130Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

A cloud native embedded storage engine built on object storage.

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

96

Reproducibility6pt70

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

Tests18pt100

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

CI/CD14pt100

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

Linting and formatting5pt100

Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).

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

  • —
    Commits (30d / 90d)
  • 250
    Forks
  • 29
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 3,130
    Watchers

Responsiveness

  • 2d 9h
    Median issue response
  • 19h
    Median PR merge time
  • 179
    Open issues
Repository files29 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/java.yaml).
    Good: Issue or PR templates present.
  • bindings
    Good: Test files detected (bindings/go/uniffi/slatedb_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
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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, cargo clippy in CI, cargo fmt in CI).
  • SECURITY.md
    Good: Security policy present.