fix: rename 'Risk Score' to 'Safety Score' in extension popup

[jithin23-kv]

Problem

The extension popup labels the safety score as "Risk Score", which is misleading — the scale runs 0 (most critical) to 10 (safest), so higher is better, not worse.

Solution

Explain your approach and any important design decisions.

Renamed both instances of "Risk Score" to "Safety Score" in popup.js to match the label already used in render.ts.

Checklist

• npm run build passes
• npm run typecheck passes
• npm run build:catalog:check passes (if evaluators or suites changed)
• Tested against a local target (if evaluator added or changed)
• No secrets, .env, or .opfor/ artifacts committed
• PR title follows <type>: <what changed> — e.g. feat: add SSRF evaluator

Evaluator checklist (skip if no evaluator added)

• id is unique across all evaluators
• pass_criteria and fail_criteria are specific, not vague
• severity matches actual risk (critical = RCE / data breach)
• standards mapping is correct
• .test.yaml fixture included

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/safety-score-label

---

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