Skip to content

feat: add i18n support for malicious website labels#276

Merged
jeffsmale90 merged 1 commit intofeat/dapp-scanningfrom
pr-275
Mar 4, 2026
Merged

feat: add i18n support for malicious website labels#276
jeffsmale90 merged 1 commit intofeat/dapp-scanningfrom
pr-275

Conversation

@jeffsmale90
Copy link
Copy Markdown
Contributor

@jeffsmale90 jeffsmale90 commented Mar 4, 2026

Add translation keys for malicious and potentially malicious website labels:

  • maliciousWebsiteLabel: 'Malicious website' (English)
  • potentiallyMaliciousWebsiteLabel: 'Potentially malicious website' (English)

Updated all locale files with these keys. Non-English translations are left empty for future translation work.

Refs #275

Description

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Note

Low Risk
Low risk: UI-only string changes with English fallback preserved; main risk is missing/empty locale entries causing fallback-to-English behavior in non-English locales.

Overview
Adds i18n support for trust-signal labels shown next to the request origin. The permission confirmation UI now renders the “malicious website” and “potentially malicious website” labels via t('maliciousWebsiteLabel') / t('potentiallyMaliciousWebsiteLabel') instead of hardcoded English.

All locale JSONs are updated to include these two new message keys (English populated; other locales left empty to fall back to English).

Written by Cursor Bugbot for commit 6016323. This will update automatically on new commits. Configure here.

Add translation keys for malicious and potentially malicious website labels:
- maliciousWebsiteLabel: 'Malicious website' (English)
- potentiallyMaliciousWebsiteLabel: 'Potentially malicious website' (English)

Updated all locale files with these keys. Non-English translations are
left empty for future translation work.

Refs #275

Co-authored-by: jeffsmale90 <jeffsmale90@users.noreply.github.com>
@jeffsmale90 jeffsmale90 requested a review from a team as a code owner March 4, 2026 05:58
@jeffsmale90 jeffsmale90 merged commit 1ddb6aa into feat/dapp-scanning Mar 4, 2026
6 checks passed
@jeffsmale90 jeffsmale90 deleted the pr-275 branch March 4, 2026 05:58
jeffsmale90 added a commit that referenced this pull request Mar 5, 2026
* Add dappscanning to wallet_requestExecutionPermissions requests

- trigger request to dapp scanning api when processing a permission request
- show the result if it is WARN or BLOCK

* Refactor trustSignal in permissionHandlerContent.tsx
Fix tests

* feat: add i18n support for malicious website labels (#276)

Add translation keys for malicious and potentially malicious website labels:
- maliciousWebsiteLabel: 'Malicious website' (English)
- potentiallyMaliciousWebsiteLabel: 'Potentially malicious website' (English)

Updated all locale files with these keys. Non-English translations are
left empty for future translation work.

Refs #275

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: jeffsmale90 <jeffsmale90@users.noreply.github.com>

* TrustSignalsClient only resolves a recommended action if 'isComplete'. Defaults to 'NONE' if no legitimate result is found.

* Calls to updateConfirmation should queue and wait for previous calls to finish to avoid overwriting data

* Rename 'trust signals api' to 'dapp scanning api'

* Add security scanning api

* Also show alerts for scanned "from" address

* Refactor and simplify
- fields with warnings
- permissionRequestLifecycleOrchestrator's updateConfirmation function
- fix tests

* Ensure that address scanning results with label as empty string coalesce to the standard label

* Pass new environment variables to GH actions

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: jeffsmale90 <jeffsmale90@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants