Source: https://seerepo.com/compare/2dust/v2rayNG/vs/open-ani/animeko
Markdown source: https://seerepo.com/compare/2dust/v2rayNG/vs/open-ani/animeko.md
Description: v2rayNG and animeko share 4 technologies: Jetpack Compose, lifecycle-runtime-ktx, androidx.core:core-ktx, and com.google.zxing:core. Both are written in Kotlin.

# v2rayNG vs animeko

v2rayNG and animeko share 4 technologies: Jetpack Compose, lifecycle-runtime-ktx, androidx.core:core-ktx, and com.google.zxing:core. Both are written in Kotlin.

- [2dust/v2rayNG](https://seerepo.com/r/2dust/v2rayNG): A V2Ray client for Android, support Xray core and v2fly core
- [open-ani/animeko](https://seerepo.com/r/open-ani/animeko): 集找番、追番、看番的一站式弹幕追番平台，云收藏同步 (Bangumi)，离线缓存，BitTorrent，弹幕云过滤。100% Kotlin/Compose Multiplatform

## What they share and what sets them apart

- In common: Jetpack Compose, lifecycle-runtime-ktx, androidx.core:core-ktx, com.google.zxing:core
- Only in v2rayNG: lifecycle-runtime-compose, androidx.appcompat:appcompat, androidx.camera:camera-compose, coil-compose
- Only in animeko: androidx.navigation3:navigation3-runtime, datastore-core, datastore-preferences, s3, androidx.datastore:datastore, Sentry, activity-ktx, lifecycle-process, adaptive-layout, adaptive-navigation, appcompat, Google, androidx.tv:tv-material, androidx.compose.material3.adaptive:adaptive, androidx.camera:camera-view, room-ktx, room-runtime, onnxruntime, onnxruntime-android, org.jsoup:jsoup, Apache, slf4j-simple, org.slf4j:slf4j-api, org.apache.logging.log4j:log4j-core

## Side by side

| | v2rayNG | animeko |
|---|---|---|
| Size | 31,634 lines written, 189 code files | 459,220 lines written, 2,299 code files |
| Who writes it | 1.2% of its commits signed by AI. With GitHub Copilot and Claude Code | 4.9% of its commits signed by AI. With Claude Code, GitHub Copilot, and Amp |
| Activity | Last push November 1, 2026, 1,678 commits, 65,340 stars | Last push November 2, 2026, 4,968 commits, 21,520 stars |
| Tests | 25 test files. 16.9% of its code files have a test that imports them | 611 test files. 44.4% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, v2rayNG or animeko?

animeko, with 459,220 lines written; v2rayNG has 31,634.

The proof: [open-ani/animeko's code at commit bd7a42f](https://github.com/open-ani/animeko/tree/bd7a42f3507606eb7ecadf8b1e71a3d8e18fda66)

### Which has more GitHub stars, v2rayNG or animeko?

v2rayNG, with 65,340 stars; animeko has 21,520.

The proof: [2dust/v2rayNG on GitHub](https://github.com/2dust/v2rayNG)

### Which has more tests, v2rayNG or animeko?

animeko, with 611 test files; v2rayNG has 25.

The proof: [open-ani/animeko's code at commit bd7a42f](https://github.com/open-ani/animeko/tree/bd7a42f3507606eb7ecadf8b1e71a3d8e18fda66)

### Which was updated more recently, v2rayNG or animeko?

animeko: its last push was on November 2, 2026, and v2rayNG's on November 1, 2026.

The proof: [open-ani/animeko's commits on GitHub](https://github.com/open-ani/animeko/commits)

### Which has more commits signed by AI, v2rayNG or animeko?

animeko: an AI signed 4.9% of its commits, with Claude Code, GitHub Copilot, and Amp; in v2rayNG, 1.2%.

The proof: [the commits each tool signed in open-ani/animeko](https://seerepo.com/r/open-ani/animeko/ai)

## Sources

- 2dust/v2rayNG: Read on November 5, 2026, at commit 57907cf (https://github.com/2dust/v2rayNG/tree/57907cf354d9769200ed4717b4430d605abe0952)
- open-ani/animeko: Read on November 5, 2026, at commit bd7a42f (https://github.com/open-ani/animeko/tree/bd7a42f3507606eb7ecadf8b1e71a3d8e18fda66)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.