This guide shows how to add a npm downloads badge for Squarespace in about a minute, with no extension: you paste one snippet into a Code Block on the page, because it belongs beside the install command, in the post or docs page that teaches it. No extension. Squarespace renders raw HTML and script tags inside a Code Block, so there is nothing to install from the Extensions marketplace.
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 Squarespace, the right spot is a Code Block 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.
On Squarespace's current plans, Code Injection (Settings → Advanced → Code Injection) is available on Core, Plus and Advanced, and on the older Business and Commerce plans, but not on Basic or the older Personal plan. Code Blocks exist on every plan, but JavaScript inside them only runs on those same higher plans, so on Basic you'll see the block but not the widget. Custom code never runs on checkout pages.
Code Injection (Settings → Advanced) needs Core, Plus or Advanced (or the older Business and Commerce plans). Code Blocks exist on every plan, but JavaScript inside them only runs on those same plans. So on Basic or the older Personal plan you see the block but not the widget — move up a plan or use a service that renders a plain image.
Squarespace renders a grey placeholder for Code Blocks while you're editing and doesn't run injected scripts in the editor at all. Save, then open the live URL in a normal tab — and hard-refresh, because Squarespace caches aggressively at the edge. Most 'it doesn't work' reports are an editor-only check.
Brine-family 7.0 templates load pages via AJAX, so a script placed in the body may not re-run when a visitor clicks through your nav — the widget appears on first load and vanishes afterwards. Fix: Site Styles → uncheck Enable Ajax Loading, or put the snippet in Code Injection Header instead so it runs once for the whole session.
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 extension. Squarespace renders raw HTML and script tags inside a Code Block, so there is nothing to install from the Extensions marketplace. Installing an extension for this would mean another dependency and update cycle just to show one widget.
A Code Block 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. Squarespace serves your site from its own CDN and the snippet is one async tag, so it loads beside your content. Prefer the Footer field over Header in Code Injection for anything script-based — it keeps the tag out of the critical path on every page at once.
Squarespace 7.1 editor: Add Block → Code. Code Injection: Settings → Advanced → Header or Footer. Page Settings: Advanced → per-page code injection on Business and above. 7.0 templates: same Code Block, plus turn off Ajax loading. 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.