What a VS Code verified publisher badge means, compared with Open VSX →
Lint pom.xml against Maven Central Portal release rules: retired OSSRH endpoints, missing POM metadata, SNAPSHOT deps, signing and jar requirements.
Daily readings on both stores, taken by us. As of 25 Sept 2026.
Each bar is one day’s change in the store’s own counter. Open VSX counts a download on every update, so a day includes updates by people who already had it.
Positions observed daily on both stores. Neither store publishes this, and the two run separate search engines over separate catalogues.
| Search | Marketplace | Open VSX |
|---|---|---|
| java | #730of 9,847 | #241of 427 |
| linters | #345of 595 | #124of 433 |
5 more searches, day-by-day history, and the extensions ranked above it. See plans | ||
VS Code Marketplace search ranking: measuring jitter and real movement →
9 releases · first published Sept 2026
Why the Open VSX download count looks inflated →
Downloads count every update, not unique installs.
Maven Central Lint - pom.xml publish requirements (sources, javadoc, GPG)’s own readme, changelog and license, as published to the VS Code Marketplace.