Skip to content

Github · GitHub Repository Radar

zed-industries zed

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

Stars

89,708

Popular Active

Forks

10,422

Watchers: 89,708

Language

Rust

License: Other

Repository Radar Score

66 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Score breakdown

  • popularity 91
  • growth 0
  • activity 100
  • freshness 100
  • community 84

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →

Zed

Zed CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Sponsorship

Zed is developed by Zed Industries, Inc., a for-profit company.

If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.

Created: Feb 20, 2021

Last push: Sep 3, 2026

Default branch: main

Latest release: v1.18.0

Languages

Share of the codebase by language, based on repository metadata from the host.

  • Rust 97.5%
  • Python 0.9%
  • Inno Setup 0.4%
  • Tree-sitter Query 0.3%
  • Shell 0.3%
  • WGSL 0.1%
  • Nix 0.1%
  • Rich Text Format 0.1%
  • Metal 0.1%
  • HLSL 0.1%
  • Handlebars 0.1%
  • PowerShell 0.1%
  • TypeScript 0.1%
  • JavaScript 0.0%
  • Dockerfile 0.0%
  • Julia 0.0%
  • HTML 0.0%
  • Objective-C 0.0%
  • Procfile 0.0%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • High absolute popularity (89,708 stars) signals broad adoption.
  • Maintained recently (last push 2 weeks ago).

Who should use it

  • Developers working primarily with Rust

Potential use cases

  • Reference or evaluate Rust open-source approaches in this domain

Strengths

  • Recent repository activity
  • README present in our index
  • Declared license: Other
  • Substantial fork count (10,422) suggests reuse and contribution interest

Limitations / considerations

  • Insights are derived from public metadata and our observations — not a substitute for code review

What to watch

  • Re-check last push, issues, and releases on GitHub before production adoption

Strong signals: Strong community interest · Active maintenance

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams