Shields.io is open-source infrastructure that renders badges for a huge number of READMEs, and nothing here is a criticism of it. The distinction is where the badge lives: Shields.io renders an SVG built for a README, while ours is HTML built for a web page, so it can be themed and styled to match the site around it.
The badge standard for READMEs. Less at home on a designed web page. Everything below was checked against shields.io in November 2026, but pricing and limits move, so confirm anything that matters on their own page before deciding.
| FeedPulse | Shields.io | |
|---|---|---|
| Price | Free, with no paid tier. | Free and open source, with no tiers at all |
| Signup | None. | None. The badge is a URL you construct |
| What you get | An HTML badge with themes that picks up your page's fonts. | A static SVG image, cached by their CDN and by GitHub's image proxy |
| Required link back | A small FeedPulse credit link under the badge. | None required |
| Cookies & privacy | No cookies. The raw IP is never stored. | No cookies; requests go to their servers |
| Customisation | Themes, plus your own CSS. It inherits your page styles. | Query parameters for colour, label and style, but it's still an image |
| Where the data lives | Star counts cached for up to six hours, then refreshed. | Pulled from the upstream API, with caching |
| Removing it | Delete the snippet. | Delete the image tag |
For a README, use Shields.io. It's the convention, it's free, it's open source, and GitHub's image proxy caches it for you. There's no argument for us inside a Markdown file, because a JavaScript widget can't run there.
Shields.io for READMEs and anywhere only an image tag is allowed. FeedPulse when the badge sits on your own site and should look like it belongs there.
Shields.io is an open-source service that turns a URL into a badge image: build status, version numbers, download counts, licence, stars and hundreds more. Because the badge is just an image URL, it works in any Markdown file, any README and any place that only accepts images. It's maintained as a community project and used across a large share of open-source projects, and for that job there's no reason to look elsewhere.
On your project's homepage the constraints flip. You can run JavaScript, you have your own fonts and colours, and a badge that looks like a README sticker can feel out of place next to a designed hero section. The FeedPulse GitHub stars badge is drawn as HTML, so it matches the page, comes in themes, and can sit inside a button or a card. It does one thing, showing the star count for one repository, rather than offering Shields.io's whole catalogue.
The sensible setup for most projects is both: Shields.io badges in the README and the docs, and the FeedPulse badge on the marketing site or landing page. Neither needs an account. If you only maintain a README, stop here and use Shields.io. FeedPulse also has an npm downloads badge built the same way, for JavaScript packages.
No FeedPulse widget sets a cookie. When a widget counts a visit, the server turns the visitor's IP address into a fingerprint using a salt that changes every UTC day, uses that fingerprint to avoid counting the same person twice within 24 hours, and never writes the raw IP address to the database. Once a day's salt expires, even we can't map a fingerprint back to an address. Location is resolved to country level only. Some widgets keep a random session ID in the browser's sessionStorage, which disappears when the tab closes, and a few remember a small preference in localStorage, such as the 'ignore my own visits' switch or the name someone typed into a comment. Whether your site needs a consent banner depends on where your visitors are and on the rest of your setup, so treat this as information for your own privacy notice, not legal advice.
Every FeedPulse widget shows a small credit link back to FeedPulse underneath it. That link is how a product with no paid tier pays for itself. It's the only thing we ask for, and it's the same for everyone because there is only one plan. If a vendor's free tier also carries branding, that's a fair like-for-like comparison. If you need a widget with no third-party link at all, a paid tool or something you build yourself is the honest answer.
Open the free GitHub stars badge page, set the options and copy the snippet. Paste it where the old Shields.io code sits today, usually a theme footer, a sidebar or a Custom HTML block, and publish. Load the page in a private window to confirm the widget renders, then delete the Shields.io code so you aren't loading both. If Shields.io holds history you care about, export or screenshot it first: FeedPulse starts counting on the day you install it and can't import another service's data. Finally, if the old tool needed an entry in your cookie banner or privacy notice, review whether that entry still applies.
The Shields.io column was checked against shields.io and its own help and pricing pages in November 2026. The FeedPulse column was checked against our own widget code, not our marketing copy. Prices, limits and plan names change, so confirm anything that affects your decision on shields.io before you rely on it. If something here is out of date, tell us through the contact page and we'll correct it. There are no affiliate links on this page, and nobody paid to be compared.
Shields.io for READMEs and anywhere only an image tag is allowed. FeedPulse when the badge sits on your own site and should look like it belongs there. For a README, use Shields.io. It's the convention, it's free, it's open source, and GitHub's image proxy caches it for you. There's no argument for us inside a Markdown file, because a JavaScript widget can't run there.
No. GitHub strips script tags in Markdown, so a JavaScript widget can't run there. Use Shields.io for the README and FeedPulse on your project's actual website, where you can style the badge to match the page.
Counts are cached for up to six hours so that a busy page doesn't hit GitHub's API on every view. Shields.io caches too, and GitHub's image proxy adds its own caching on README badges, so neither shows the count to the exact second.
Nothing. There is no paid tier, no card on file and no account. Widgets have no traffic cap. A few SEO tools that pay for their data per lookup have a small daily fair-use allowance per visitor, which resets every day.