What is kotlinx.coroutines built with?

kotlinx.coroutines is a Kotlin repo built with org.jetbrains.kotlin:kotlin-stdlib-jdk8 and Google. It is tested with org.jetbrains.kotlinx:kotlinx-coroutines-test, junit:junit, and org.junit.jupiter:junit-jupiter-api and runs in production with org.slf4j:slf4j-api. It has 114,525 written lines, with 669 test files.

Read on November 9, 2026, at commit ead0821. Read it as markdown

The card says what it's built with. Its whole map opens it up: every part of the code and how it connects to the rest.

Support

The base 2

Testing 3

  • org.jetbrains.kotlinx:kotlinx-coroutines-test
  • junit:junit259 files
  • org.junit.jupiter:junit-jupiter-api9 files

Deploy 1

Tools 8

  • JetBrains
  • OpenJDK
  • androidx.annotation:annotation1 file
  • org.openjdk.jol:jol-core1 file
  • atomicfu-gradle-plugin
  • blockhound
  • dokka-gradle-plugin
  • gradle-animalsniffer-plugin

Other 11

  • com.google.guava:guava
  • org.jetbrains.kotlinx:kotlinx-coroutines-android
  • org.reactivestreams:reactive-streams16 files
  • io.reactivex.rxjava3:rxjava10 files
  • net.bytebuddy:byte-buddy1 file
  • byte-buddy-agent
  • jna
  • jna-platform
  • kotlinx-coroutines-debug
  • reactor-core
  • rxjava

Other repos with a similar stack

Ordered by how much of its stack they share with kotlinx.coroutines, then by stars.

Frequently asked questions

What language is kotlinx.coroutines written in?
kotlinx.coroutines is written in Kotlin, with 114,525 written lines.
What framework does kotlinx.coroutines use?
kotlinx.coroutines is built with org.jetbrains.kotlin:kotlin-stdlib-jdk8 and Google.
Does kotlinx.coroutines have tests?
Yes. kotlinx.coroutines has 669 test files and is tested with org.jetbrains.kotlinx:kotlinx-coroutines-test, junit:junit, and org.junit.jupiter:junit-jupiter-api.
Which repos have a stack like kotlinx.coroutines's?

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.Private repo? Sign in with GitHub

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →