Independent analytics for a public GitHub repository
Xray, Penetrates Everything. Also the best v2ray-core. Where the magic happens. An open platform for various uses. — view on GitHub · t.me/projectXray
Language
Go
License
MIT
open source
Created
Nov 2020
Stars
41,693
Forks
5,899
Issues
27 open
Updated 21 Sept 2026, 01:49 UTC
tracker score 67/100 methodology →
Computed from release cadence, responsiveness, backlog trend and contributor depth.
Last release
177 days ago
v26.3.27
Cadence
every 47.7d
177d gapPR merge median
3.0d
Issue response median
2.7h
Commits / 7d
3
The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.
Reading: delivery held at ~31 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.
How fast maintainers answer, review and merge — ranked against repos of similar size and age.
Issue first non-author response
median 2.7hcohort: n/aPR first review
median 2.4hcohort: n/aPR merge time
median 3.0dcohort: n/aBots excluded Sample: 96 merged PRs (90d) / 68 recent issues. Percentile position measured from the left — shorter is faster.
25
first-time PRs (12 mo)
88%
got a response
n=245 scanned
0%
were merged
64 newcomer candidates
24%
returned ≤90d
verified via author historyVerdict: tough room for newcomers — only 88% of verified first-time PRs got a maintainer-class response and 0% merged (window 2026-03-25..2026-06-23). The core team ships fast, but drive-by PRs mostly sit open.
top 1 — 23.7% of accepted changes · last commit Sep 13
top 3 — 59.5% of accepted changes
long tail — 46 further authors
Verdict: low key-person risk. 49 human commit authors in 12 months; top author (Fangliding) holds 23.7%, top 3 hold 59.5%, 11 authors above 1% each.
Open issues and pull requests right now. Trend history builds from daily tracking.
open issues & PRs — right now
27
open issues
27
open pull requests
Tracking daily since 25 Aug 2026 — 21 snapshots so far.
54 open
27 issues + 27 PRs · backlog down 27% over 27d
5,899 forks · 0 with independent momentum
GFW-knocker/Xray-core — 260★ · last push 2d ago
XTLS/Xray-core is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.
If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.
0 stable releases in 90d (median gap 47.7d)
Issue response sits at a 2.7h median — up from 0.5h 27d ago
License unchanged · not archived · no rename/transfer
Max release gap in 12mo: 54d (cadence 47.7d median)
These answers regenerate on every snapshot — they never rot.
Partially — activity is slowing (score 67/100). Last stable release v26.3.27 177 days ago, 3 commits in the last full week, median PR merge 3.0d. Evidence collected Mon Sep 21 2026.
MPL-2.0 — as reported by GitHub.
v26.3.27, 177 days ago. Median gap between stable releases is 47.7 days; 0 stable releases shipped in the last 90 days — the current 177d gap is well above that median.
On the evidence: caution. 49 human authors in 12 months, no fork-succession pressure. Caveat for contributors: the newcomer funnel is weak (0% first-PR merge rate). Not published to npm — GitHub activity only.
Link preview (auto-generated OG card)
tracker.git.tools
XTLS/Xray-core
SLOWING · 67/100
ships every 47.7d · PR merge 3.0d · ★ 41,693
XTLS/Xray-core — maintenance verdict & repo intelligence · tracker.git.tools
README badge (live SVG — every embed is a backlink)
[](https://tracker.git.tools/XTLS/Xray-core)
Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.
Get an email the week this repo’s verdict changes — release droughts, response-time decay, key-person exits. Free for 3 repos. Your whole package.json monitored, on paid.
This report for your private org repos →Verdict-change alerts, release droughts, response-time decay. Free for 3 repos.
Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.