GoBadge Dynamic: From Module Stats to Universal Badges
GoBadge has evolved from a tool focused on Go modules to a versatile badge generation system. The new dynamic endpoint allows users to create badges from any JSON API, expanding its utility significantly. Users can now badge various metrics from platforms like GitHub, npm, and Docker, or even their own APIs.
- ▪GoBadge originally supported three specific endpoints for Go modules.
- ▪The new dynamic endpoint enables badge creation from any JSON API.
- ▪Users can badge metrics from GitHub, npm, Docker, and their own APIs.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/cinfinitedev_engine/gobadge-dynamic-from-module-stats-to-universal-badges-361l |
| Publication time | Mon, 25 May 2026 20:38:22 +0000 |
| Retrieval time | 2026-05-25T21:07:40.563Z |
| Last seen | 2026-05-25T21:07:40.563Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | sQ6ba61Jwtlb |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3780619) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } CinfiniteDev Posted on May 25 GoBadge Dynamic: From Module Stats to Universal Badges #npm #webdev #product #opensource What started as a tool for Go modules just became something much bigger. The Big Idea GoBadge started with three endpoints — stars, imports, imported-by. Useful if you write Go. Not so useful if you don't. Today that changes. The new dynamic endpoint lets you turn any JSON API into a badge.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).