01 · Roasts
Kernel warehouse
Three roughly 2 GB Android kernel trees demonstrate serious scope; repository-level CI and tests are still mostly missing.
Commit afterburner
2,031 yearly commits and a dense heatmap make the activity claim credible, not just bio-powered.
Adoption lag
GrayRavens-GKI carries 15 of 37 total stars; most other substantial projects still have zero visible users.
Docs unevenness
Nubia recovery documentation is solid, while android_unisoc_tuner ships CI and tests without even a README.
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% weight62C
- Consistency20% weight80A
- Quality20% weight65C
- Depth15% weight58D
- Breadth10% weight55D
- Community10% weight55D
03 · Stats
365-day commit heatmap
305 active days
Language distribution
- C98%
- Assembly1%
- Shell0%
- Makefile0%
- Python0%
- Perl0%
- Other1%
04 · Numbers
Owned repos
non-fork
63
Commits
last 12 months
2,031
Followers
36
Joined GitHub
Jun 2024
05 · Top repos
XTENSEI /
kernel_common_5.10
A 1.99 GB Android Common Kernel 5.10 source mirror with substantial architectural scope and patch guidance, but only 3 stars, no sampled source files, tests, CI, or license evidence.
XTENSEI /
kernel_common_5.15
A very large Android 13 Linux 5.15 common-kernel fork with Bazel/Kleaf build definitions, extensive Qualcomm module and ABI configuration, and kernel formatting tooling, but no tests, CI, or declared license.
XTENSEI /
android_device_nubia_Z2577
A substantial, documented Nubia V80 Max TWRP device tree with automated builds and Android recovery patches, but it has no stars, license, tests, or clear external adoption.
XTENSEI /
kernel_common_5.4
A very large Android Common Kernel 5.4 source tree with documented patch requirements, but no demonstrated adoption, tests, CI, or license metadata; its scale provides substantial architectural depth despite the one-day snapshot.
XTENSEI /
android_device_tecno_LJ6
A substantial LineageOS TECNO LJ6 device tree with Android build, HAL, init, VINTF, power, thermal, audio, and proprietary-blob integration, but only 2 stars and no tests, CI, license, or typed implementation.
XTENSEI /
android_unisoc_tuner
A substantial Unisoc Android tuning module with GPU/CPU/DVFS controls, watchdog and browser UI, backed by a shell self-check and GitHub Actions, but currently has no adoption, documentation, license, or sustained history.
XTENSEI /
GrayRavens-GKI
A documented Android 5.10 GKI kernel release tree with substantial scheduler, VM, DAMON, KMI, and governor tuning, but limited visible adoption and no automated validation or licensing artifacts.
XTENSEI /
research-game-G10
A substantial Phaser educational RPG prototype with three explorable biomes, procedural art, dialogue, riddles, punctuation and arcade puzzle systems, but it remains a newly shipped, unadopted JavaScript project without tests or CI.
XTENSEI /
twrp_device_infinix_X6885
A substantial but explicitly WIP PBRP device tree for the Infinix HOT 60 PRO, with Android build configuration, recovery init/fstab rules, and custom MTK boot-control utilities, but no demonstrated adoption or validation pipeline.
06 · Timeline
- Jun 28, 2024Joined GitHub
- Dec 27, 2025Created GrayRavens-GKI — Gray Ravens GKI releases
- Feb 21, 2026Created twrp_device_infinix_X6885 — PBRP DEVICE TREE FOR INFINIX HOT 60 PRO (X6885) ( STILL WIP DONT BUILD )
- May 5, 2026Created kernel_common_5.10 — GrayRavens Zenithed Common Kernel Source
- Jun 21, 2026Created android_device_tecno_LJ6 — TECNO POVA 7 (LJ6) Device Tree
- Aug 7, 2026Created kernel_common_5.15 — GrayRavens Zenithed kernel for android13-5.15
- Aug 9, 2026Created android_device_nubia_Z2577
- Aug 19, 2026Created kernel_common_5.4 — GrayRavens-Zenithed Common kernel 5.4
- Aug 30, 2026Created research-game-G10
- Sep 26, 2026Created android_unisoc_tuner — test
- Sep 26, 2026Most recent push to android_unisoc_tuner
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.