docs(readme): drop the broken Dependabot badge, note Dependabot in Contributing - #154
Merged
Merged
Conversation
…ntributing The badge had been rendering as a bare label with no icon. It is not an icon problem: the URL returns HTTP 500 and the SVG literally reads "dependabot: 404". badgen's /dependabot/ endpoint served the old standalone Dependabot.com service, which GitHub acquired and shut down; Dependabot is now built into GitHub and no longer exposes that API, so badgen gets a 404 upstream. Not recoverable by changing the URL -- the data source is gone. Verified the rest of badgen is fine, so nothing else needs touching: the release, stars and npm badges all return 200 (and already show v0.13.0). Replaced with a sentence in Contributing, where it is information for contributors -- explaining why automated PRs show up -- rather than decoration. "We use Dependabot" is not something a reader evaluating the library needs from a badge, unlike release/npm/CI/codecov which say something about project state. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Dependabot badge had been rendering as a bare label with no icon. It turns out it is not an icon problem — the URL returns HTTP 500 and the SVG literally reads
dependabot: 404:badgen's
/dependabot/endpoint served the old standalone Dependabot.com service, which GitHub acquired and shut down. Dependabot is now built into GitHub and no longer exposes that API, so badgen gets a 404 upstream. Not recoverable by changing the URL — the data source no longer exists.Scope check: the rest of badgen is fine
Verified before touching anything, so no other badge needs changing:
github/releaserelease: v0.13.0github/starsstars: 12npm/vnpm: v0.13.0dependabot(Nice side effect: the release and npm badges already show the fresh 0.13.0.)
What replaces it
A sentence in Contributing, where it is information for contributors — explaining why automated PRs appear and that they follow the same CI and review as anything else — rather than decoration:
"We use Dependabot" is not something a reader evaluating the library needs from a badge, unlike release / npm / CI / codecov, which each say something about project state. And a broken badge costs more credibility than a ninth working one would add.
Docs only — one line removed, one added.
🤖 Generated with Claude Code