This guide shows how to add a npm downloads badge for Ghost in about a minute, with no integration: you paste one snippet into an HTML card in the editor, because it belongs beside the install command, in the post or docs page that teaches it. No integration to configure. Ghost renders raw HTML and script tags from Code injection and from an HTML card, so there is nothing to install and no third party in the loop.
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 Ghost, the right spot is an HTML card in the editor. 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.
Code injection is available on every Ghost(Pro) plan and on self-hosted Ghost, both sitewide (Settings → Code injection) and per post. HTML cards are available in the editor on all plans too. The main limit is on Ghost(Pro)'s entry plan, which doesn't allow custom themes, so use code injection or HTML cards rather than editing theme files.
Ghost's whole appeal is speed. Putting a script in Site Header makes the browser deal with it before painting your post; Site Footer runs it after. Our snippet is async either way, so use the Footer box unless the widget must exist before first paint (the heatmap and the speed badge are the only two that benefit).
An HTML card displays the raw code while you're writing and only renders on the published page. That's by design, not a failed paste. Publish (or use the preview link) and check the live URL — and remember post-level code injection doesn't run in preview at all on some versions.
If you paste the snippet into a `.hbs` file, the next theme update or theme switch silently removes it. Code injection is stored in your Ghost settings, not in the theme, so it survives both. On Ghost(Pro) you can't edit theme files directly anyway — Code injection and HTML cards are the whole surface.
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 integration to configure. Ghost renders raw HTML and script tags from Code injection and from an HTML card, so there is nothing to install and no third party in the loop. Installing an integration for this would mean another dependency and update cycle just to show one widget.
An HTML card in the editor, 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. Ghost is already the fastest mainstream publishing platform and the point is to keep it that way: the snippet is one async tag, so it never blocks your post from rendering. Site Footer is the right injection slot for script tags — Site Header is for things that must run before paint.
Ghost admin: Settings → Code injection → Site Footer. Ghost editor: insert an HTML card. Post settings: per-post Code injection fields. Self-hosted themes: edit default.hbs above {{ghost_head}}. 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.