xai-org/grok-build
diegosouzapw/OmniRoute
docker-desktop-windows/docker-desktop
safishamsi/graphify
cslol-manager/ltk-manager
// OWNER · zhulin025 · REPO SNAPSHOT
zhulin025
一个复古QQ风格的 Codex 皮肤
zhulin025STARS39+0 · 7d
FORKS4+0 · 7d
CONTRIBUTORS0maintainer graph thin
OPEN ISSUES · PRS0· 0
LICENSE—no license file
LANGUAGEJavaScript
FOUNDED—
LOCATION—
MEMBERS—
PUBLIC REPOS—
TOTAL STARS—
FOCUS—
FUNDING—
//STAR HISTORY · 12M
+43 all-time-window
Stars · cumulative43 · today
//WHY IT'S TRENDING· narrative synthesis · medium confidence
zhulin025/Codex-QQ-Skin is sitting at #977 on the trending leaderboard with a pulse of 12/100 with no cross-source channels firing yet — GitHub-stars-only signal so far.
It sits at 39 stars without a fresh weekly delta on record — the trending placement here is steady-state interest in the JavaScript other space rather than a 7-day breakout.
Watch-outs: no tagged release on record (treat as pre-stable).
↻ refreshed 57m ago· next sync in 8m· sourced from 0 channels · 0 mentions / 24h
// RELATED REPOS · CROSS-SOURCE OVERLAP
#01
pbakaus/impeccable
JavaScript ecosystem peer.
CO-MENTIONS · 30D (10 total)
10#02
Anil-matcha/Open-Generative-AI
JavaScript ecosystem peer.
CO-MENTIONS · 30D (7 total)
7#03
ilysenko/codex-desktop-linux
JavaScript ecosystem peer.
CO-MENTIONS · 30D (1 total)
1#04
zhangjanice66/Codex-QQ-2007
JavaScript ecosystem peer.
CO-MENTIONS · 30D (0 total)
0
#05
ChatGPTBox-dev/chatGPTBox
JavaScript ecosystem peer.
CO-MENTIONS · 30D (0 total)
0
▌ FAQ · answers from the data spine
What is zhulin025/Codex-QQ-Skin?
一个复古QQ风格的 Codex 皮肤
Who maintains Codex-QQ-Skin?
Maintained by zhulin025 (the owner) on GitHub.
What language is Codex-QQ-Skin written in?
Primarily JavaScript.
When was Codex-QQ-Skin created? When was the last update?
Created July 17, 2026 · last commit July 18, 2026.
How do I install Codex-QQ-Skin?
Clone the repo:
git clone https://github.com/zhulin025/Codex-QQ-Skin.gitIs Codex-QQ-Skin actively maintained?
stalled — no commits for an extended period
Created
Updated
Last commit
//COMMENTS · 0
Sign in to join the discussion