zed-industries/zed
Grade a repo

89

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 14% of 5,156 graded repos

Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

Documentation87
Engineering85
Health100
Rust86,711Other23d ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  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

87

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

85

CI/CD14pt57

CI is configured (.github/workflows/community_close_stale_issues.yml).

Reproducibility6pt80

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

Tests18pt100

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

Linting and formatting5pt100

Rust linting configured (.prettierrc).

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

  • 657 / 2559
    Commits (30d / 90d)
  • 9,439
    Forks
  • 1000
    Releaseslatest 3y ago

Community

  • 87% - Good
    Community health
  • 7 bus factor
    authors own >50% of commits
  • 86,711
    Watchers

Responsiveness

  • 27d 23h
    Median issue response
  • 4h
    Median PR merge time
  • 3,356
    Open issues
Repository files53 root entries
  • .agents
  • .cargo
  • .cloudflare
  • .config
  • .factory
  • .github
    Good: CI is configured (.github/workflows/community_close_stale_issues.yml).
    Good: Issue or PR templates present.
  • .zed
  • assets
    Good: Licensed under Other.
  • ci
  • crates
    Good: Test files detected (crates/agent/src/tests).
  • docs
  • extensions
  • legal
  • nix
  • script
  • tooling
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .prettierrc
    Good: Rust linting configured (.prettierrc).
  • .rules
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • compose.yml
    Good: Environment pinned via compose.yml.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
  • debug.plist
  • default.nix
  • Dockerfile-collab
  • Dockerfile-collab.dockerignore
  • Dockerfile-cross.dockerignore
  • Dockerfile-distros
  • Dockerfile-distros.dockerignore
  • flake.lock
  • flake.nix
  • GEMINI.md
  • LICENSE-APACHE
  • LICENSE-GPL
  • livekit.yaml
  • lychee.toml
  • Procfile
  • Procfile.web
  • 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.
  • renovate.json
  • REVIEWERS.conl
  • rust-toolchain.toml
  • rustfmt.toml
  • shell.nix
  • typos.toml
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/zed-industries/zed)](https://www.repo-grade.com/report/zed-industries/zed)

More graded Rust repos