badgemaxxing

badgemaxxing

Badges that live in the URL.

Write the text, colors and animation into a link, paste it in your README, and the badge draws itself. No account, no files, no tracking.

The linkdraws

    Make

    Make a badge

    Everything you choose goes into the link, so the badge in your README is exactly the one you see here.

    1 Write it
    2 Animate it optional, and they stack

    Check

    How maxxed is your README?

    Paste a public GitHub repo. Your browser asks GitHub for its README directly; nothing goes through badgemaxxing.

    Try rust-lang/rust (brutal), vitejs/vite or your own repo.

    How it works

    The link is the badge

    Nothing is stored anywhere. The server reads the link and draws the badge when GitHub asks for it.

    Write the badge into the link

    /badge/v1/<label>-<message>-<color>.svg. Use _ for a space, -- for a dash and __ for an underscore.

    
              

    Add options

    style, labelColor, emoji (percent-encoded), logo (a brand like rust, with logoColor or logoColor=brand), size (0.5 to 4), anim (any of 64, comma-separated, they stack), speed (0.25 to 4) and compact=1 to keep an animated badge at its normal size.

    
              

    It never changes under you

    The v1 is the version the link was made with. New looks get a new version, so a badge you paste today stays exactly the same. Prefer a file in your repo? Fetch it once and commit it.

    
              

    Add yours to the gallery

    Add one line to crates/core/data/community.txt and open a pull request. Copy catalog line in the builder writes it for you.

    # label | message | color | emoji | your-github-handle
    vibes|immaculate|#ec4899|✨|your-github-handle