OrganizationLichess
@lichess-org • The free and open source chess server. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
71%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
17 repositories updated in the last 90 days.
Leading language
Unknown
Portfolio mix
Unknown (7), TypeScript (6), Python (3)
Average size
13
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-10-15(10d ago)GitHub API fallback30 repositories
71%
of the visible star count comes from this organization's top three repositories.
13
stars per repository in this same snapshot.
Unknown
is the most common language here, with 17 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Balanced portfolio across 30 reposTop 3 share 71%
Organization pages work best when you separate portfolio breadth from flagship concentration. In Lichess's case, the visible top three repositories account for about 71% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Unknown (7), TypeScript (6), Python (3). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | lichess-org/berserk Python client for the lichess API | Python | 169 |
| 2 | lichess-org/stockfish-web WebAssembly builds for Stockfish, for lichess.org | Python | 68 |
| 3 | lichess-org/papers Papers that use Lichess data, study Lichess, or cite Lichess | TeX | 44 |
| 4 | lichess-org/broadcaster Broadcast your chess games on Lichess! | Vue | 23 |
| 5 | lichess-org/leroyjenkins Follow ban logs to manage ip sets in nftables | Rust | 22 |
| 6 | lichess-org/api-ui some web UIs on top of the Lichess API | TypeScript | 22 |
| 7 | lichess-org/dart-multistockfish Multiple flavors of Stockfish Chess Engine | C++ | 11 |
| 8 | lichess-org/files Public downloads | 11 | |
| 9 | lichess-org/flutter-sound-effect Flutter plugin to play short sounds with low latency | Swift | 7 |
| 10 | lichess-org/lifat large assets used by lila in production but optional for dev builds | JavaScript | 6 |
| 11 | lichess-org/liplay A collection of scala web libraries that originated from play framework, and are dedicated to powering lila | Scala | 3 |
| 12 | lichess-org/op1 Probe Marc Bourzutschky's partial 8-piece tablebase, op1 | C | 2 |
| 13 | lichess-org/lichess-org.github.io | 2 | |
| 14 | lichess-org/TypeMap type-level map in Scala3, using macros | Scala | 2 |
| 15 | lichess-org/picfit An image resizing server written in Go | Go | 2 |
| 16 | lichess-org/flutter-soundpool Soundpool plugin for Flutter | Dart | 2 |
| 17 | lichess-org/lichess-web-theme | CSS | 1 |
| 18 | lichess-org/dart-lc0 lc0 | C++ | 1 |
| 19 | lichess-org/research | 0 | |
| 20 | lichess-org/bbb-calendar | TypeScript | 0 |
| 21 | lichess-org/changelog Changelog generator for lichess-org repos | TypeScript | 0 |
| 22 | lichess-org/inbound-email | TypeScript | 0 |
| 23 | lichess-org/hermes CRUD service for email templates, with an edit UI | TypeScript | 0 |
| 24 | lichess-org/team | Scala | 0 |
| 25 | lichess-org/docker-nginx Our nginx docker build | 0 | |
| 26 | lichess-org/nftnl-rs Rust bindings and abstraction for libnftnl, low-level userspace access to the in-kernel nf_tables subsystem | 0 | |
| 27 | lichess-org/fishnet-assets NNUE files built into https://github.com/lichess-org/fishnet | 0 | |
| 28 | lichess-org/zerofish | TypeScript | 0 |
| 29 | lichess-org/vosk-browser A speech recognition library running in the browser thanks to a WebAssembly build of Vosk | 0 | |
| 30 | lichess-org/namecheck | Python | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.