methodology
How we collect, compare and qualify the public evidence behind VSXRank.
Publisher guide ·
How to compare your VS Code extension's growth with competitors
Compare VS Code extension installs fairly: pick real peers, match dates, use window gains and percentages, handle decreases and gaps, and keep registries apart.
Read story
Publisher guide ·
What changed before a competitor overtook your VS Code extension?
A dated method for a Marketplace rank drop: rule out jitter, check how many queries moved, list both listings' edits, and log what happened in the window.
Read story
Publisher guide ·
What does the VS Code Marketplace install count actually mean?
What the VS Code Marketplace install count includes, why updates are excluded, why it can fall, and what 1.9 million daily readings show about decreases.
Read story
Publisher guide ·
VS Code Marketplace search ranking: measuring jitter and real movement
Learn how VS Code Marketplace search ranking varies between identical searches, how to filter jitter, and which listing fields to review.
Read story
Publisher guide ·
Why a VS Code extension rank tracker needs a 1,000-position window
A VS Code extension rank tracker needs a defined search window. Learn what positions 1–1,000 reveal and how to interpret every missing state.
Read story
Publisher guide ·
Why the Open VSX download count looks inflated
Open VSX download count measures package downloads, not unique people. Learn what it can show, what it cannot, and how to compare registry trends.
Read story
Data report ·
How many VS Code extensions are there? The September 2026 catalogs
A 6 September 2026 snapshot counted 115,150 Marketplace listings and 17,429 on Open VSX. See the overlap, method, and limits.
Read story