chore: recolor slsa badge to brand blue

[shenxianpeng]

What

Recolors the SLSA 3 badge in the profile README to match the other badges (brand blue #2c9ccd).

Why

The original badge from slsa.dev has its own fixed colors (dark gray + green) that don't match the badge row. slsa.dev does support a ?color= query param, but only for its built-in palette — ?color=2c9ccd is ignored, so it can't be recolored there.

Change

-[![SLSA 3](https://slsa.dev/images/gh-badge-level3.svg)](https://slsa.dev)
+[![SLSA 3](https://img.shields.io/badge/SLSA-3-2c9ccd.svg)](https://slsa.dev)

A shields.io badge keeps the same two-segment layout (gray SLSA label + blue value) and the same link to https://slsa.dev, but the value segment now renders in the same #2c9ccd as the PyPI / License / Website badges.

Note: commit-check-action/README.md has the same slsa.dev badge (?color=blue) — that's a separate repo; happy to apply the same change there if you want.

[coderabbitai]

Warning

Review limit reached

@shenxianpeng, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d20f5b1f-9370-4692-8457-34377378028a

📥 Commits

Reviewing files that changed from the base of the PR and between c4ee108 and eb6973d.

📒 Files selected for processing (1)

• profile/README.md

---

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.}

[github-actions]

Commit-Check ❌

--- PR Title:
Type subject_imperative check failed ==> chore: recolor slsa badge to brand blue 
Commit message should use imperative mood (e.g., 'fix bug' not 'fixed bug', 'add feature' not 'adding feature')
Suggest: Change the first verb to imperative form, e.g., 'fix' instead of 'fixed'/'fixes'/'fixing' 

--- Commit 1/1:
Type subject_imperative check failed ==> chore: recolor slsa badge to brand blue 
Commit message should use imperative mood (e.g., 'fix bug' not 'fixed bug', 'add feature' not 'adding feature')
Suggest: Change the first verb to imperative form, e.g., 'fix' instead of 'fixed'/'fixes'/'fixing'