01 · Roasts
Hook, line, and sinker
Vector has 12,374 stars and 826 forks. At this point the Android runtime is probably filing bug reports against you.
Test suite witness protection
Vector, NeoZygisk, ChromeXt, Demo, and PlayIntegrityFix ship CI but no tests. The pipeline is immaculate; the assertions remain theoretical.
Security-tooling constellation
Vector, TEESimulator, NeoZygisk, ChromeXt, and pixel-ksu-root make one thing clear: Android internals did not consent to this level of scrutiny.
Horizontal builder confirmed
209 recent commits sampled across repositories and 660 commits this year: apparently one complicated codebase was not enough.
Built using
Zoral
Shadows one worker for a week, then takes over their job with zero extra setup. Behaves exactly like the original.
zoral.ai
02 · Category breakdown
- Impact25% weight88A
- Consistency20% weight65C
- Quality20% weight69C
- Depth15% weight65C
- Breadth10% weight80A
- Community10% weight80A
03 · Stats
365-day commit heatmap
240 active days
Language distribution
- Jupyter Notebook37%
- Mathematica30%
- HTML8%
- TeX4%
- Kotlin4%
- C++4%
- Other13%
04 · Numbers
Owned repos
non-fork
30
Commits
last 12 months
660
Followers
2,474
Joined GitHub
Dec 2016
05 · Top repos
JingMatrix /
NeoZygisk
A widely adopted Android root-injection module with 2,267 stars and 179 forks, combining C++ ptrace/PLT injection with a Rust daemon, mount-namespace isolation, module loading, and companion-process IPC.
JingMatrix /
Vector
Vector is a widely adopted, actively evolved Kotlin/NDK Android hooking framework with 12,374 stars and 826 forks, multi-process Binder infrastructure, legacy Xposed compatibility, native ART/dex2oat hooks, and automated release distribution.
JingMatrix /
ChromeXt
ChromeXt is a maintained Kotlin/Xposed Android module with 1,136 stars that injects UserScript and DevTools support across Chromium and WebView browsers, backed by substantial hook, parser, storage, and WebSocket code.
JingMatrix /
TEESimulator
A widely adopted Android security tooling project with 2,396 stars and 305 forks, implementing Android 10–14 KeyMint interception, a Rust reference TA, Kotlin daemon, WebUI validation, and release automation.
JingMatrix /
Demo
A substantial Android/C++ security-detection demo with 121 stars and 28 forks, combining three probe contexts, native mount reconciliation, linker integrity checks, and reproducible Android CI.
JingMatrix /
PlayIntegrityFix
A real Android/Zygisk native module with 66 stars, CI packaging, and substantial C++/shell implementation for Play Integrity property spoofing, but no tests and limited evidence of broad external adoption.
JingMatrix /
KMAXPP05
A substantial French-language ML teaching repository, combining Beamer lectures, solved TDs, seven TP materials, and a final project brief; it is well organized and documented but lacks tests, CI, and an explicit license, with minimal visible adoption.
JingMatrix /
pixel-ksu-root
A substantial, hardware-verified Pixel rooting research tool: GhostLock reaches temporary KernelSU root, while five additional CVE paths are documented as hunts or partial chains, with a disciplined runner and offset tooling.
06 · Timeline
- Dec 9, 2016Joined GitHub
- Dec 11, 2022Created ChromeXt — UserScript and DevTools supports for Chromium based and WebView based browsers
- Jul 20, 2023Created Vector — Modern Xposed Framework
- Nov 30, 2024Created Demo — A demo app to detect Zygote injections
- Dec 17, 2024Created NeoZygisk — Zygote injection with ptrace
- Aug 21, 2025Created PlayIntegrityFix — Spoof bootloader property (Android OS layer only) and Play Integrity verdict
- Aug 29, 2025Created TEESimulator — Software simulation for Android hardware-backed key pairs with key attestation
- Feb 6, 2026Created KMAXPP05 — Ressources pédagogiques pour le module KMAXPP05 - Machine Learning.
- Aug 25, 2026Created pixel-ksu-root — CVE research and exploits to help gaining roots for Pixel devices
- Sep 11, 2026Most recent push to pixel-ksu-root
07 · Compare
08 · Rubric
How this score was produced
Overall = Σ (category × weight) + gentle top-end curve
Tier thresholds
▸ How the pipeline works
- 01Scrape.Pull every non-fork repo pushed in the last 90 days, plus your contribution calendar, followers, and language byte counts — straight from GitHub's REST & GraphQL APIs.
- 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
- 03Grade each repo. All repos run in parallel through a fast scoring model that reads the picked files and rates each one independently on Impact, Quality, and Depth — with evidence citations.
- 04Aggregate. A larger reasoning model combines the per-repo scores with server-computed stats (heatmap, commit cadence, language entropy, follower count) to produce the 6-dimension profile score + roasts.
- 05Correct.Deterministic server-side checks enforce anchor-scale floors (e.g. a profile with 2,000+ public commits can't score 30 Consistency) and recompute the final verdict.
~90 seconds per profile, ~$0.25 in compute. Total of ~240 files read across your top-12 repos. One rating per GitHub account per day.
▸ Data sources & caveats
- Heatmap & commit totals: GitHub GraphQL
contributionsCollection— covers the last 365 days, includes private repos when the user has opted in (default). - Language %: byte totals across the top 30 owned non-fork repos.
- Curve: a small upward nudge centered on raw score ≈ 70, capping at 100. Prevents specialists from being unfairly penalised for narrow breadth.
- Anchor corrections: when server-measured signals (e.g. privateWorkLikely, multiRepoVolume, follower count) mandate a minimum category score, the aggregation step enforces it. These are signal-conditional, not identity-based floors.