This guide shows how to add a npm downloads badge for Wix in about a minute, with no app: you paste one snippet into an Embed a Widget element on the page, because it belongs beside the install command, in the post or docs page that teaches it. No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for.
The npm downloads badge shows how many times a package was downloaded in the last day, week or month, using npm's public download counts. It's for JavaScript library authors who want that number on their docs or landing page, not only on npmjs.com. Scoped packages are supported.
On Wix, the right spot is an Embed a Widget element on the page. Put it next to the install command, in the docs page or post that teaches people to use the package. That's where a reader is deciding whether to run npm install.
Wix has two routes. The Embed a Widget element (Add → Embed Code) works on every plan, including free sites, and runs the widget inside its own frame. Settings → Custom Code, which adds a script to every page, only works on a Premium plan with a connected domain. On a free wixsite.com address the Custom Code section is visible but doesn't run, so use the embed element instead.
Wix only unlocks Settings → Custom Code on a published site with a connected domain, which in practice means a Premium plan. On a free wixsite.com address the section is there but inert. The embed element has no such requirement, so free sites are not locked out — they just can't use the head position. One more trap: if you later change or reassign the domain, Wix deletes your custom code snippets, so keep the snippet saved somewhere.
Every Wix embed runs in a sandboxed iframe that cannot talk to the parent page, so auto-resize scripts do nothing. If the widget looks cut off, the widget is fine and the element is too short: drag the blue handles or type a pixel height in the layout panel. Do it again in the mobile editor, because Wix stores mobile sizing separately. Set the height to the tallest the widget will ever get to avoid layout shift.
The editor and even Preview mode do not run custom code, and embeds frequently render blank in Preview. Publish, then open the live URL in a normal tab. A widget that 'doesn't work' on Wix is almost always an unpublished change or a Preview-mode check. Also make sure your snippet is HTTPS-only — Wix blocks mixed content outright.
Download counts include automated installs from CI systems and mirrors, so they overstate the number of people using a package. Use them as a relative signal, not a user count.
No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for. Installing an app for this would mean another dependency and update cycle just to show one widget.
An Embed a Widget element on the page, because it belongs beside the install command, in the post or docs page that teaches it.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Wix drops the embed into its own sandboxed iframe, so it physically cannot block your page from rendering — the trade-off is that you set the height yourself, because a sandboxed iframe can't tell the parent page how tall it needs to be. There is no cache to purge; the change goes live when you hit Publish.
Wix Editor: Add (+) → Embed & Social → Embed a Widget. Wix Studio: Add → Embed → Custom Embeds, same dialog. Editor X: use the HTML iFrame element. Wix Blog: add an HTML block inside the post. Any builder with a raw-HTML or code block will render it.
No. They include automated installs from build servers and mirrors, so treat them as a rough popularity signal rather than a count of people.