GitLab: Configure access to GitLab NPM Registry
Verified publisherWhat a VS Code verified publisher badge means, compared with Open VSX →
It allows to configure access to GitLab NPM Registry from your workstation whenever you are working on repo where npm dependencies should be fetched from Gitlab NPM registry
Tracked since 5 Sept 2026
Daily readings on both stores, taken by us. As of 24 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. Days before 5 Sept are reconstructed from public archives rather than read by us.
Where GitLab: Configure access to GitLab NPM Registry ranks in search
Positions observed daily on both stores. Neither store publishes this, and the two run separate search engines over separate catalogues.
| Search | Marketplace | Open VSX |
|---|---|---|
| node | #682of 1,459↓5 7d | — |
| npm | #169of 616↑2 7d | #119of 143↓3 7d |
2 more searches, day-by-day history, and the extensions ranked above it. See plans | ||
VS Code Marketplace search ranking: measuring jitter and real movement →
- Installs
- 2,871+0.1% 7d
- Rating
- —unrated
- Rank in SCM Providers
- #111of 1,668
- Latest
- v0.0.117 Jan 2021
12 releases · first published Nov 2020
Why the Open VSX download count looks inflated →
- Downloads
- 4,200+0.9% 7d
- Rating
- —from 0 reviews
- Rank in SCM Providers
- #103of 510
- Latest
- v0.0.117 Jan 2021
Downloads count every update, not unique installs.
What the publisher says
GitLab: Configure access to GitLab NPM Registry’s own readme, changelog and license, as published to the VS Code Marketplace.