Lapce
@lapce • Open source projects from lapce. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
98%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
1 repositories updated in the last 90 days.
Leading language
Rust
Portfolio mix
Rust (17), Unknown (9), HTML (1)
Average size
214
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-01-28(220d ago)GitHub API fallback30 repositories
98%
of the visible star count comes from this organization's top three repositories.
214
stars per repository in this same snapshot.
Rust
is the most common language here, with 1 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 66% of its visible star count.
Flagship share 66%Breakout repo: floem
Organization pages work best when you separate portfolio breadth from flagship concentration. In Lapce's case, the visible top three repositories account for about 98% 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 Rust (17), Unknown (9), HTML (1). 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 | lapce/floem A native Rust UI library with fine-grained reactivity | Rust | 4.3K |
| 2 | lapce/lapdev Seamless dev environments for Kubernetes | Rust | 2K |
| 3 | lapce/tiron Reasonable Automation Engine | Rust | 109 |
| 4 | lapce/lapce-volts | Rust | 14 |
| 5 | lapce/lapce-extensions Extension registry for https://lapce.dev | Rust | 12 |
| 6 | lapce/atom-one Atom One Theme | 10 | |
| 7 | lapce/floem-shadcn shadcn/ui inspired components for Floem | Rust | 9 |
| 8 | lapce/tree-sitter-grammars | Rust | 9 |
| 9 | lapce/plugin-server-protocol Defines a common protocol for plugin servers. | HTML | 9 |
| 10 | lapce/cosmic-text Pure Rust multi-line text handling | Rust | 6 |
| 11 | lapce/lapce-lldb | Rust | 4 |
| 12 | lapce/lapce-docs | 4 | |
| 13 | lapce/snapcraft-lapce | 4 | |
| 14 | lapce/wasi-experimental-http Experimental outbound HTTP support for WebAssembly and WASI | Rust | 4 |
| 15 | lapce/floem-tailwind Tailwind-style utility methods for Floem styling | Rust | 3 |
| 16 | lapce/vger-rs 2D GPU renderer for dynamic UIs | Rust | 3 |
| 17 | lapce/homebrew-lapce | Ruby | 3 |
| 18 | lapce/psp-types | Rust | 3 |
| 19 | lapce/hcl-rs HCL parsing and encoding libraries for rust with serde support | 2 | |
| 20 | lapce/rcl A reasonable configuration language | Rust | 1 |
| 21 | lapce/locale_config Rust crate to maintain locale preferences for process and thread and initialising them by inspecting the system for user preference. | 0 | |
| 22 | lapce/dap-types A Rust implementation of the Debug Adapter Protocol | 0 | |
| 23 | lapce/charset-normalizer-rs Truly universal encoding detector in pure Rust - port of Python version | 0 | |
| 24 | lapce/human-sort Humansort implementation in rust | 0 | |
| 25 | lapce/glazier | Rust | 0 |
| 26 | lapce/import-codesign-certs GitHub Action for Importing Code-signing Certificates into a Keychain | TypeScript | 0 |
| 27 | lapce/xcode-staple Xcode Staple | JavaScript | 0 |
| 28 | lapce/lsp-types Types for communicating with a language server | Rust | 0 |
| 29 | lapce/font-kit A cross-platform font loading library written in Rust | Rust | 0 |
| 30 | lapce/glutin A low-level library for OpenGL context creation, written in pure Rust. | 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.