Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This commit fixes a bug in the Cake Wallet Litecoin wallet where, when renaming a wallet, stored MWEB (a privacy feature for Litecoin) transaction records were being copied to a new storage box by reusing the exact same object references. …
Data migration now clones objects instead of sharing referencesPrevents potential state corruption when renaming Litecoin walletsNo explicit input validation or cryptographic change present
This is a routine update to the project's automated iOS build pipeline. It changes which Apple computer (runner) and Xcode version are used to compile and upload the iPhone app, so the app meets Apple's upcoming App Store requirement to us…
This commit is a routine mix of small fixes and test-tool updates. It makes a UI key more specific to avoid list-item conflicts, adds a safety check before showing a post-transaction popup, updates a test helper to match new app settings, …
Flutter BuildContext used across async gap now guarded by context.mountedNo explicit security keywords, CVE references, or advisory links in commit or titleChanges are split across UI, test tooling, and fixture scripts with no coherent security theme
This is a large accessibility and test-automation improvement for the Cake Wallet Flutter app. It adds stable identifiers to buttons, text fields, lists, and dialogs so screen readers and automated UI tests can find them. The patch also re…
Removed user-data interpolation from accessibility identifiers (tx ids, wallet names, seed words, addresses)Added stable, index-based or enum-based semantics identifiers across UI componentsAdded custom lints and CI workflow to prevent future user-data interpolation in test keys
This commit adds three new automated testing pipelines for the Cake Wallet mobile app: one for Android, one for iOS, and a weekly overnight test. These are explicitly marked as 'reply-only' experiments, meaning a failure will not block rel…
New CI/CD pipeline handling wallet seed phrases and API keysUse of `NO_REPLY` / `continue-on-error: true` to avoid blocking mergesExplicit mitigation: avoids `npx` on macOS to prevent environment-variable leakage via process title
This is a large cleanup of how the app labels its on-screen buttons and fields for automated testing and accessibility tools. Previously, many test labels were accidentally built from private user data such as wallet names, transaction IDs…
Accessibility identifiers derived from PII/sensitive data (wallet names, transaction IDs, seed words, addresses) are replaced with static or index-based identifiersNew custom lint rule no_string_interpolation_in_test_key blocks string interpolation in test keys except for int indexes and enum .nameNew custom lint rule require_test_key_semantics_identifier ensures framework interactive widgets with _key keys expose a Semantics identifier
This is a very large code refactor of the cryptocurrency swap/exchange feature in Cake Wallet. It rewrites how exchange rates are fetched, how trades are created and tracked, and how trade history is stored in the local database. The commi…
Large-scale rewrite of trade creation, rate fetching, and status monitoringDatabase schema migration for Trade table with data reconstruction from old columnsNew amount parsing helper (Money.safeParse) and exchange-rate math (ExchangeRate.fromAmounts)
This commit expands Cake Wallet's Lightning Bitcoin feature so it works across multiple Bitcoin accounts instead of being locked to the primary account only. It also fixes address selection so the app picks an unused Segwit address that be…
Account isolation logic changed: Lightning and Segwit address selection now account-awarePrevious code could return a Segwit address from a different account than the one currently selectedRemoval of hard-coded account index checks suggests prior account-boundary assumptions were too restrictive
This commit is a large internal refactor of how Bitcoin-style wallets in Cake Wallet store and derive account keys. It replaces scattered maps of HD keys with a single shared 'ElectrumAccounts' model, initializes those keys earlier during …
Refactor of BIP32 HD key derivation and account key storage across multiple coin modulesWallet keys view model now exposes master xPrv and xPub instead of per-account private keyChange in how legacy change HDs are identified, with a new regression test for Litecoin MWEB change addresses
This commit deletes four leftover Android Java files that were no longer used. The app's namespace was already fixed to 'com.cakewallet.cake_wallet', so these old copies of the main activity and application class under different package na…
This commit fixes visual layout bugs in the Cake Wallet mobile app where long Tamil translations were being drawn off-screen or clipped. It also fixes a broken unit test by adding a missing mock object. There is no security vulnerability h…
This commit adds new language translations (Bengali, Marathi, Tamil, Telugu), fixes Hindi translations, and introduces automated tools to check translation quality. It also makes a small formatting fix so cryptocurrency amounts display wit…
No changes to cryptographic, authentication, networking, or storage codeNo permission changes or new entitlementsNo changes to dependency versions or external URL endpoints
This commit is a routine user-interface redesign for the Cake Wallet app. It adds a new 'More Actions' menu (a floating plus button), moves Contacts and Buy/Sell options into that menu, and introduces first-time explainer pop-ups for gift …
No security-relevant code changes identifiedUI-only refactor with no new network, storage, or crypto logicNew URL launch to cakepay.com in gift card explainer uses standard url_launcher external application mode
This commit improves accessibility for screen-reader users. It adds spoken labels to buttons that were previously unlabeled, announces which cryptocurrency each wallet holds, removes a duplicate invisible tap target, and makes the currentl…
This commit improves screen-reader accessibility in the Cake Wallet mobile app. It makes settings switches announce their name (e.g., 'Auto generate addresses, switch, off') and makes choice options like 'Enabled / Tor only / Disabled' tel…
This commit makes small GitHub workflow and documentation tweaks. It adds read-only permissions to four pull-request check workflows, deletes an already-commented-out lint workflow, and updates a Windows installer filename and release note…
Workflow least-privilege hardening: four PR workflows now declare read-only repository permissionsRemoval of an inactive lint workflow that contained commented-out build steps and external download commandsDocumentation-only update for Windows installer filename and release history
This commit is a routine version bump and changelog update for the Cake Wallet/Monero.com v6.5.4 release candidate. It updates translated changelog text, version/build numbers across Android, iOS, Linux, and macOS, and makes minor UI fixes…
This commit fixes a bug in how Cake Wallet signs Bitcoin-style messages. Previously, the app could not correctly sign messages with 'change addresses' (a special type of address used when sending leftover funds back to yourself). The fix m…
Refactor centralizes address validation and derivation-path construction for hardware signingChange addresses are now included in address lookup, fixing a functional signing bugTaproot and MWEB addresses are explicitly rejected for message signing
This commit fixes a bug in Cake Wallet's Bitcoin message signing. Previously, if a user chose a silent payment address (a newer privacy-focused Bitcoin address type), the app would still sign the message using the wallet's main key. That s…
Cryptographic signature produced for a different identifier than the one presented to the userSilent fallback to main wallet key when selected address cannot be derivedMessage signing bypass for silent payment / unheld addresses
This commit is a straightforward user-interface performance fix. It wraps each tab of the app's main dashboard in a Flutter widget called TickerMode, which pauses animations in tabs that are not currently visible. Before the change, a load…
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Lower-priorityfix height of details modal when adding note from send confirmation (#3413)by malik1004x · 5dfae0e1 · Jul 18, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · malik1004x
fix height of details modal when adding note from send confirmation (#3413)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
* feat: add Trezor passphrase support for wallet restoration process
* revert: send page changes
* chore: format code
* chore: format code
* chore: reorganize imports and improve code formatting in send_page.dart [skip ci]
* auto-reformat
* fix: trezor usb device refresh race condition
* fix: ui bugs in relation to trezor
* fix: only show passphrase option for trezor devices
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com> Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · Low 25/100
This commit adds support for using a passphrase with Trezor hardware wallets when restoring a Monero wallet in Cake Wallet. It also fixes a small race condition when refreshing the list of connected USB devices. There is no clear security vulnerability in the diff itself; it is a feature addition with some minor hardening.
* feat: add Lightning transaction URL support in transaction details view model
* fix: update currency selection logic in WalletAddressListViewModel and ReceivePage
* feat: integrate computed transaction amount and fee getters in TransactionDetailsViewModel, refactor CopyWrapper logic in TransactionDetailsModal
* refactor: apply lint rules
* refactor: apply lint rules and improve LNURL handling with new methods for withdrawal requests and error checks
* auto-reformat
* fix: receive_page regression
* fix: Withdraw lightning to other btc wallet gives LN address
* chore: update .lock files [skip ci]
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com> Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100
This is a routine feature and bug-fix update for Cake Wallet's Lightning (Bitcoin layer-2) support. It adds the ability to handle LNURL withdrawal requests, fixes currency selection when receiving Bitcoin vs Lightning, and cleans up transaction-detail display. There is no clear security vulnerability in the diff, but the new network code that calls external Lightning services and parses invoices is a place where future bugs could matter, so it deserves normal review and testing.
* feat: rescan on zkool fix: sending to extracted addresses fix: labeling shielding txs fix: autoshield endless loop fix: autoshield t addr not firing fix: autoshield destinations chore: remove old routes for rescan with zkool other minor fixes/cleanups
* chore: bump zkool2 to latest version fix: reduce amount of taddrs generated fix: derivation path for internal wallets fix: display address in correct hidden/usable spots fix: get wallet db height before it syncs for the first time fix: taddr rotation with passphrase fix: sync progress ui refresh fix: taddress generation not getting capped fix: hidden addresses not being hidden fix: pending transactions not being shown fix: t address cache misses fix: t address rotation not getting refreshed fix: t address high index not being used
* fix: refresh t addresses
* fix: patch rust side to make t addr rotation work
* fix: ui issue in recipient address fix: zcash multiaddress send to show in the ui fix: potential race condition
* minor fixes
* format
* fix: flashing on receive screen
* remove unused 'autoShield'
* review
71/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlcryptography-sensitive pathsigning or wallet path
AI analysis · Low 44/100
This is a large feature commit that replaces Cake Wallet's older Zcash wallet backend (warp_api) with a new library called zkool2. It touches address generation, transaction creation, balance scanning, transparent-address rotation, auto-shielding, and migration of old wallets. The commit message lists many bug fixes, but the code change is broad and partially complete (for example, the rescan method is mostly commented out). There is no direct evidence in the commit of a deliberate security vulnerability, but the size and incomplete state create a higher-than-normal risk of bugs that could lose funds, leak privacy, or produce incorrect balances.
Lower-priorityfix context passed to navigatorby Robert Malikowski · 8616824c · Jul 17, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Robert Malikowski
fix context passed to navigator
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedadd spaceby Robert Malikowski · 07d78b0a · Jul 17, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
add space
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit fixes a simple Dart syntax error by adding a missing space between the keyword `const` and `BorderRadius.only`. It is a cosmetic/code-correctness change with no security relevance.
AI review queuedmergeby Robert Malikowski · 108363c5 · Jul 17, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
merge
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit adds a single optional parameter named `bottomText` to a user-interface widget class. It is a straightforward code change with no visible security relevance.
AI review queueddart fixby Robert Malikowski · fa9229ec · Jul 17, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
dart fix
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine code cleanup of a single Dart file in the Cake Wallet app's buy/sell screen. It changes quote styles on imports, adds 'const' keywords, reformats function bodies, and reorders constructor parameters. There is no change to app behavior, no bug fix, and no security relevance visible in the diff.
Lower-prioritywrap in popScope to prevent error on back button pressby Robert Malikowski · 59eb3d79 · Jul 17, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Robert Malikowski
wrap in popScope to prevent error on back button press
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Lower-priorityfix: Wrong fiat for sent tx from swaps (#3409)by David Adegoke · 3070612f · Jul 17, 2026 · 2 filesMessage 88 · StrongTriage 0Details
Commit message · David Adegoke
fix: Wrong fiat for sent tx from swaps (#3409)
* fix android CI
* fix: wrong fiat amount showing for sent tx from swaps
* fix: use token address to fetch fiat amount for pending send entry
88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queueddelete solana sync keys when removing the walletby Omar · c10ce20c · Jul 16, 2026 · 1 fileMessage 45 · ThinLow 47Details
Commit message · Omar
delete solana sync keys when removing the wallet
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 47/100
This commit fixes a cleanup issue in Cake Wallet's Solana support. When a user deleted a Solana wallet, the app left behind leftover 'last synced signature' data stored on the device. This patch now deletes those leftover records when the wallet is removed. It is a privacy/data-hygiene fix rather than a remote hack vulnerability.
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com> Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 23/100
This commit fixes bugs in how Cake Wallet connects to Ledger hardware wallets. It adds guards so the app doesn't crash or behave oddly when no Ledger connection exists, prevents duplicate connection attempts, improves cleanup when switching wallets, and updates the underlying Ledger Bluetooth/USB library versions. There is no obvious new security vulnerability here; the changes look like stability and reliability improvements for hardware wallet users.
* add incremental sync, parallel fetch for native and spl token, and other improvments on perf and display regarding lagging
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit is a routine performance and reliability improvement for Solana wallets in Cake Wallet. It makes transaction syncing faster by only fetching new signatures since the last sync, batches network requests, prevents duplicate refreshes, and fixes a few small UI calculation bugs. There is no clear security vulnerability being patched, and the changes do not appear to introduce one.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is purely a code-formatting cleanup. It adjusts line breaks, indentation, and whitespace across many Dart files but does not change any program logic, add new features, or alter security behavior.
Security candidateReformat the whole codebase with 100 line width (#3403)by Omar Hatem · 16ddc083 · Jul 14, 2026 · 801 filesMessage 58 · ThinInformational 15Details
Commit message · Omar Hatem
Reformat the whole codebase with 100 line width (#3403)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100
This commit is a purely cosmetic reformatting of the entire codebase to use a 100-character line width. It adjusts whitespace, line breaks, and indentation across hundreds of files but does not change any program logic, security behavior, or functionality. The only non-formatting change is that the GitHub Actions lint workflow was disabled by commenting it out, which is a CI/process change rather than a product security issue.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100
This is a large automated code reformatting commit. It only changes whitespace, line breaks, indentation, and trailing newlines across hundreds of files. There is no change to program logic, no bug fixes, and no security-related behavior change.
feat: add allowedIp to moonpay signature generation (#3375)
75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Low 26/100
This commit updates how Cake Wallet builds payment links for MoonPay, a service that lets users buy or sell cryptocurrency inside the app. The app now asks its own backend server to produce the full signed payment URL, instead of adding the cryptographic signature itself on the device. The backend can now also restrict the link to the user's IP address. The change is a feature/refactor; there is no direct evidence in the commit that it fixes an active security vulnerability.
Remove broken feature request discussion link (#3336)
Remove the extra GitHub issue contact link that pointed to a broken Discussions category.
The repository already has a working Feature request issue template, so the duplicate Feature or Enhancement Request contact link created a confusing entry in the issue creation modal and led users to a failing GitHub Discussions URL.
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference