[ryanduguid]

Summary

The README badges now load from sources GitHub's image proxy can reach, so they no longer show as broken images.

GitHub serves external README images through its camo proxy, which returned 504 after about 4.2 s on most shields.io fetches on 30 October 2026. Each badge keeps its link target and alt text:

• GitHub Actions status: the provider's own badge. GitHub's native workflow badges are not proxied and have GitHub's grey label.
• Static badges (licence.svg, fork-of.svg, rust.svg): the exact shields.io SVGs, committed under .github/assets/badges/ and linked by relative path.
• ATTRIBUTION.toml and ATTRIBUTION.md list the 3 committed badge SVGs, as the asset policy requires. Each records the original shields.io URL and Apache-2.0, the licence of badges/shields.

Evidence

• Before: shields.io badge URLs fetched through camo mostly returned 504.
  After: each replacement URL returned 200 SVG on 5 of 5 fetches through camo; on this branch at a 375 px viewport all 17 non-banner images decoded.
• Checks: cargo xtask assets first failed because each new SVG needs an ATTRIBUTION.toml entry; entries were added (source: the original shields.io URL, licence Apache-2.0 as badges/shields, SHA-256) and ATTRIBUTION.md regenerated with cargo xtask assets --write; then cargo xtask assets: ok, cargo test -p xtask: 42 passed.

Merge danger

Door: two-way. Blast radius: README

Unverified

• The GitHub mobile app itself; the 375 px browser check stands in for it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud