This guide shows how to add a npm downloads badge for Blogger in about a minute, with no third-party gadget: you paste one snippet into the post editor, switched to HTML view, because it belongs beside the install command, in the post or docs page that teaches it. Nothing to install. Blogger's own HTML/JavaScript gadget takes raw markup, which is all this needs — and unlike a theme edit, a gadget survives changing your theme.
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 Blogger, the right spot is the post editor, switched to HTML view. 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.
Blogger is free, and every method here works on every blog, on blogspot.com or a custom domain. The HTML/JavaScript gadget is the safest place for most widgets, because gadgets survive theme changes. Editing the theme's HTML also works, but it's parsed as XML, so a snippet with stray characters can stop the theme from saving.
Blogger themes are parsed as XML, so characters like &, <, > and quotes inside a script can trigger errors such as "The reference to entity must end with the ';' delimiter" and refuse to save. Our snippet is a plain async script tag with no bare ampersands, so it pastes cleanly — but if you ever hit that error, wrap the code in //<![CDATA[ ... //]]> or encode the five reserved characters. This is the main reason to prefer a gadget over a theme edit.
The post editor has two modes. Compose escapes anything that looks like markup, so the snippet renders as visible text instead of a widget. Switch to HTML view before pasting, and avoid flipping back to Compose afterwards — Blogger sometimes rewrites the markup when it converts between the two.
Changing theme, restoring a backup or applying one of Blogger's own themes replaces the whole template, taking any code you pasted into it with it. Gadgets live in your layout settings instead, so they survive. Unless you specifically need the <head> position, use a gadget.
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.
Nothing to install. Blogger's own HTML/JavaScript gadget takes raw markup, which is all this needs — and unlike a theme edit, a gadget survives changing your theme. Installing a gadget for this would mean another dependency and update cycle just to show one widget.
The post editor, switched to HTML view, 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. Blogger is served by Google's own infrastructure and the snippet is one async tag, so it loads after your post is already on screen. There's no cache to purge — saving a gadget publishes it immediately.
Layout editor: Add a Gadget → HTML/JavaScript. Theme editor: Edit HTML, paste above </head> or </body>. Post editor: switch to HTML view, then paste. Blogger mobile app: not supported — use the desktop dashboard. 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.