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
10 repositories updated in the last 90 days.
Leading language
Kotlin
Portfolio mix
Kotlin (13), Unknown (7), Java (2)
Average size
36
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
71%
of the visible star count comes from this organization's top three repositories.
36
stars per repository in this same snapshot.
Kotlin
is the most common language here, with 10 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Organization pages work best when you separate portfolio breadth from flagship concentration. In ktor.io'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 Kotlin (13), Unknown (7), Java (2). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | ktorio/ktor-documentation Documentation for the Ktor framework. | Kotlin | 539 |
| 2 | ktorio/ktor-cli Command-line tool for creating Ktor projects | Go | 139 |
| 3 | ktorio/ktor-plugin-registry Maintains a repository of all Ktor plugins | Kotlin | 87 |
| 4 | ktorio/ktor-build-plugins Ktor Plugins for Build Systems | Kotlin | 83 |
| 5 | ktorio/ktor-chat Example for a large, full-stack application using the latest and greatest | Kotlin | 57 |
| 6 | ktorio/ktor-klip Library improvement proposals for new features in Ktor | Markdown | 48 |
| 7 | ktorio/ktor-websockets-chat-sample Ktor Chat App using WebSockets | Kotlin | 43 |
| 8 | ktorio/ktor-get-started-sample | Kotlin | 20 |
| 9 | ktorio/ktor-io Collection of IO primitives to work with network and files written in Kotlin using kotlinx.coroutines library | Kotlin | 12 |
| 10 | ktorio/ktor-build Repository that hosts TeamCity Configuration for entire Ktor project | 12 | |
| 11 | ktorio/kastle Kotlin application source templating / layout engine | Kotlin | 9 |
| 12 | ktorio/ktor-gradle-sample | Kotlin | 7 |
| 13 | ktorio/ktor-benchmarks | HTML | 7 |
| 14 | ktorio/ktor-for-xyz Ktor for XYZ tutorial | Kotlin | 7 |
| 15 | ktorio/ktor-maven-sample | Kotlin | 4 |
| 16 | ktorio/ktor-answers | Kotlin | 3 |
| 17 | ktorio/FrameworkBenchmarks Source for the TechEmpower Framework Benchmarks project | C++ | 3 |
| 18 | ktorio/ktor-exposed-hands-on | Kotlin | 2 |
| 19 | ktorio/opentelemetry-java-instrumentation OpenTelemetry auto-instrumentation and instrumentation libraries for Java | Java | 1 |
| 20 | ktorio/homebrew-ktor | Ruby | 1 |
| 21 | ktorio/HttpArena The most complete HTTP open source benchmarking platform. Don't just say you're fast, prove it. | C# | 0 |
| 22 | ktorio/ktor-starters | 0 | |
| 23 | ktorio/openapi-generator OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3) | Java | 0 |
| 24 | ktorio/homebrew-core-3 ๐ป Default formulae for the missing package manager for macOS (or Linux) | 0 | |
| 25 | ktorio/homebrew-core-2 ๐ป Default formulae for the missing package manager for macOS (or Linux) | 0 | |
| 26 | ktorio/homebrew-core-1 ๐ป Default formulae for the missing package manager for macOS (or Linux) | 0 | |
| 27 | ktorio/winget-pkgs The Microsoft community Windows Package Manager manifest repository | PowerShell | 0 |
| 28 | ktorio/homebrew-core ๐ป Default formulae for the missing package manager for macOS (or Linux) | Ruby | 0 |
| 29 | ktorio/brew ๐บ The missing package manager for macOS (or Linux) | 0 | |
| 30 | ktorio/angular-realworld-example-app Exemplary real world application built with Angular | 0 |
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.