ytsaurus/ytsaurus

0

/ 100

Documentation86
Engineering86
Health100
C++2,195Apache-2.01d ago
Grade a repo

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

YTsaurus is a scalable and fault-tolerant open-source big data platform.

Documentation

86

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.

README12pt85

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

86

Tests18pt80

Test files detected (build/config/tests).

Reproducibility6pt80

Lockfile present (contrib/go/_std_1.25/src/crypto/internal/fips140/aes/_asm/ctr/go.sum). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/build-jobs.yaml).

Linting and formatting5pt100

Linter or formatter configured (build/config/tests/ruff/ruff.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (build.gradle.kts).

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)
  • 206
    Forks
  • 134
    Releaseslatest 2y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,195
    Watchers

Responsiveness

  • 3d 2h
    Median issue response
  • <1h
    Median PR merge time
  • 486
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/build-jobs.yaml).
    Good: Issue or PR templates present.
  • build
    Good: Test files detected (build/config/tests).
    Good: Linter or formatter configured (build/config/tests/ruff/ruff.toml).
  • certs
  • cmake
  • connectors
  • contrib
    Good: Lockfile present (contrib/go/_std_1.25/src/crypto/internal/fips140/aes/_asm/ctr/go.sum). Installs are reproducible.
    Good: Environment pinned via contrib/go/_std_1.25/src/crypto/internal/boring/Dockerfile.
  • .arcadia.root
  • .gitignore
    Good: .gitignore present.
  • .mapping.json
  • .piglet-meta.json
  • AUTHORS
  • build.gradle.kts
    Good: Dependency manifest found (build.gradle.kts).
  • BUILD.md
  • clang.toolchain
  • CMakeLists.darwin-arm64.txt
  • CMakeLists.darwin-x86_64.txt
  • CMakeLists.linux-aarch64.txt
  • CMakeLists.linux-x86_64.txt
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • conanfile.py
  • 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.
  • 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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.