Pixiv-Shaft vs Magisk
Pixiv-Shaft and Magisk share 6 technologies: core-ktx, androidx.core:core-splashscreen, room-ktx, room-runtime, io.noties.markwon:core, and com.jakewharton.timber:timber. Both are written in Kotlin.
What they share and what sets them apart
CeuiLiSA
Pixiv-Shaft
Pixiv第三方Android客户端
Kotlin8.3kRead on November 17, 2026, at commit c151431What is Pixiv-Shaft built with?Only in Pixiv-Shaft
- androidx.fragment:fragment-ktx
- androidx.activity:activity-ktx
- com.tencent:mmkv-static
- Firebase
- com.google.dagger:hilt-android
- lifecycle-livedata-ktx
- lifecycle-process
- lifecycle-runtime-ktx
- cardview
- constraintlayout
- Toaster
- androidx.recyclerview:recyclerview
- androidx.appcompat:appcompat
- com.google.android.flexbox:flexbox
- androidx.swiperefreshlayout:swiperefreshlayout
- androidx.interpolator:interpolator
- de.hdodenhof:circleimageview
- androidx.biometric:biometric
- Glide
- okhttp3-integration
- androidx.documentfile:documentfile
- jp.wasabeef:glide-transformations
- org.jsoup:jsoup
In common
- core-ktx
- androidx.core:core-splashscreen
- room-ktx
- room-runtime
- io.noties.markwon:core
- com.jakewharton.timber:timber
topjohnwu
Magisk
The Magic Mask for Android
Kotlin64.1kRead on November 17, 2026, at commit 70d233cWhat is Magisk built with?Only in Magisk
- Jetpack Compose
- androidx.activity:activity
- androidx.navigationevent:navigationevent-compose
- androidx.navigation3:navigation3-runtime
- androidx.window:window-core
- androidx.lifecycle:lifecycle-viewmodel-navigation3
- androidx.navigation3:navigation3-ui
- activity-compose
- lifecycle-runtime-compose
- material3-adaptive-navigation-suite
- androidx.compose.animation:animation
- com.google.accompanist:accompanist-drawablepainter
Google- androidx.compose.material:material-icons-extended
Side by side
Pixiv-ShaftMagisk
SizeLines written by people and agents, without generated ones; code files, without tests.
Pixiv-Shaft320,909 lines written1,392 code files
Magisk43,581 lines written189 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
Pixiv-Shaft46.1% of its commits signed by AIWith Claude Code and Codex
Magisk0.7% of its commits signed by AIWith Cursor and Claude Code
ActivityFrom GitHub and its history, on the day SeeRepo read it.
Pixiv-ShaftLast push November 17, 20264,058 commits8,324 stars
MagiskLast push November 14, 20267,868 commits64,082 stars
TestsThe files that test the code, and the share of code files a test imports.
Pixiv-Shaft403 test files39.2% of its code files have a test that imports them
Magisk6 test files9.5% of its code files have a test that imports them
Frequently asked questions
Which is bigger, Pixiv-Shaft or Magisk?
Pixiv-Shaft, with 320,909 lines written; Magisk has 43,581.
Which has more GitHub stars, Pixiv-Shaft or Magisk?
Magisk, with 64,082 stars; Pixiv-Shaft has 8,324.
The proof: topjohnwu/Magisk on GitHub
Which has more tests, Pixiv-Shaft or Magisk?
Pixiv-Shaft, with 403 test files; Magisk has 6.
Which was updated more recently, Pixiv-Shaft or Magisk?
Pixiv-Shaft: its last push was on November 17, 2026, and Magisk's on November 14, 2026.
The proof: CeuiLiSA/Pixiv-Shaft's commits on GitHub
Which has more commits signed by AI, Pixiv-Shaft or Magisk?
Pixiv-Shaft: an AI signed 46.1% of its commits, with Claude Code and Codex; in Magisk, 0.7%.
The proof: the commits each tool signed in CeuiLiSA/Pixiv-Shaft
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

