The Trust Score badge

How to add it

1. Open your repository's page on ClaudeWave. When the page is in our search index, a Trust Score badge block near the end of the page has your snippet ready.
2. Copy the Markdown version for a README, or the HTML version anywhere HTML is allowed.
3. Paste it into your README and commit. The image updates on its own when the score changes.

The image lives at https://claudewave.com/api/badge/<slug>, where the slug is owner/repo in lowercase with every other character turned into a hyphen.

MarkdownCopy

[![ClaudeWave Trust Score for affaan-m/ECC](https://claudewave.com/api/badge/affaan-m-ecc)](https://claudewave.com/en/repo/affaan-m-ecc)

HTMLCopy

<a href="https://claudewave.com/en/repo/affaan-m-ecc"><img src="https://claudewave.com/api/badge/affaan-m-ecc" alt="ClaudeWave Trust Score for affaan-m/ECC" width="320" height="64"></a>

What the badge shows

A number from 0 to 100 and a verdict. The verdict is a band of the number, except that a deep review classing the repository as a risk sets it to Avoid whatever the number says. Counts are today's catalogue.

A repository with no score yet, or a link to something no longer in the catalogue, shows a neutral "Not rated" badge instead of a broken image.

How the score is computed

Every repository gets a rule-based score from its public GitHub metadata and README. No model is involved in this part. It starts at 50, adds or subtracts points for each signal below, is rounded and kept between 0 and 100.

• Licence: +15 for a recognised open-source licence, +5 for another declared licence, -10 with none. A licence file GitHub cannot identify adds nothing and is flagged.
• Maintenance, by last push: +15 under 30 days, +10 under 90, +5 under 180, -5 between 180 days and a year, -15 over a year.
• Stars and forks, above 100 stars: -25 when forks are under 0.5% of stars on a repository with more than 1,000 stars (possible bought stars), +10 above 5%, +5 above 2%.
• Description: +5 for 30 to 350 characters, -5 with none.
• Topics: +5 for three or more, -3 with none.
• Owner: +15 for an owner on a fixed list of official publishers (for example anthropics and modelcontextprotocol).
• Age: +5 when older than a year, -20 when younger than 30 days with more than 5,000 stars.
• Open issues: -5 with more than 500 open and no push in 90 days.
• Archived: -30.
• README: +5 when longer than 500 characters, -3 with none.
• Install instructions that pipe a remote script into a shell (curl | sh): -8.
• Suspicious patterns in the README: -10 for one or two, -25 for more than two.

Deep security review

Some repositories also get a deep security review of their files, with its own 0 to 100 score and a safety class. A review is only accepted when each concern quotes material that was actually inspected. For those repositories the published score is 40% the rule-based score and 60% the review, rounded.