docs(readme): serve stars, downloads and license badges from badgen.net

[zereight]

shields.io is intermittently failing on these three badges ("Unable to select next GitHub token from pool", "rate limited by upstream service", "license: invalid"). Switch them to badgen.net, which renders the same data. README badges only; no code changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 617d3f6b-cef3-42a5-b118-9dce3f7e366a

📥 Commits

Reviewing files that changed from the base of the PR and between 81581c1 and 847403b.

📒 Files selected for processing: 1

• README.md

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout: 9

• GitHub Check: schema-tests
• GitHub Check: code-quality
• GitHub Check: integration-test
• GitHub Check: docs-build
• GitHub Check: test
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (ruby)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (actions)

🔇 Additional comments: 1

README.md: 1

3-4: LGTM!

Also applies to: 6-6

📝 Summary

Summary by CodeRabbit

• Documentation
  • Updated the GitHub stars, npm downloads, and license badges to use Badgen. The npm version badge is unchanged.

The README now uses Badgen image URLs for the GitHub stars, npm downloads, and GitHub License badges. The npm version badge is unchanged.

Changes: README badges

Layer / File(s)	Summary
Badge image sources README.md	The GitHub stars, npm downloads, and GitHub License badges now use Badgen image URLs. The npm version badge is unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: agent-hellboy

Merge Risk: ⚪ Minimal · up to 84740

The README’s stars, downloads, and license badges now use Badgen and display the intended information. No concrete issue remains that should block merging.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly and concisely identifies the README badge migration from shields.io to badgen.net.
Description check		The description directly explains the badge reliability issue, the switch to badgen.net, and the README-only scope.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

✨ Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[zereight]

Cursor CLI review (gitlab-mcp-maintainer skill, serious issues only): no findings. README badge hosts only; all three badgen.net URLs return valid SVGs matching the shields.io data (stars, monthly downloads, MIT). No runtime, default, auth, or output change.