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.
51/100 average clarity
33Strong · 80–100
316Adequate · 60–79
513Thin · 40–59
191Opaque · 0–39
33security candidates with opaque commit messaging
This commit fixes a mobile UI bug where pressing Cancel on a 'building transaction' dialog accidentally closed one too many screens. The fix moves the responsibility for closing the dialog into each screen's cancel handler, and prevents er…
No security-relevant signals in the diffUI-only navigation and error-dialog suppression changesNo cryptographic, authentication, authorization, or data-handling changes
This commit is a routine merge from the project's staging branch into a feature branch. The visible code changes fix small UI/UX bugs in Stack Wallet's send screens: clearing an internal address-validation cache when the form is reset, mak…
Clearing stale address-provider state on form reset reduces the risk of stale validation data influencing a subsequent transactionFee-form caching prevents repeated network calls and accidental fee UI flicker/state races on rebuildQR scan buttons are UX additions with no visible parser/validation logic changes
This commit fixes a desktop wallet bug where the send-fee form would repeatedly re-fetch fee estimates on every screen rebuild, wasting resources and possibly flickering. It now caches the fee estimate and only retries if the previous fetc…
No security-relevant signals present in diff or commit metadataChange is a UI/UX performance and reliability improvement
This commit merges a feature branch into another work-in-progress branch. It adds QR-code scanning buttons to two desktop token send screens and resets an internal address-validation state variable when the send form is cleared. There is n…
State reset added to clearForm() to avoid stale validation dataNew QR scan entry points in token send flows (UI feature, not a vulnerability signal)
This change fixes a UI state bug in the cryptocurrency wallet's send form. When a user clears the send form, the app now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing…
UI state desynchronization between form field and validity indicatorPotential user confusion from stale valid-address stateNo input validation, cryptographic, or network-layer changes
This commit adds a QR code scanner button to two desktop cryptocurrency send forms. It is a straightforward user-interface feature addition with no apparent security relevance.
This commit adds a missing QR code scan button to two desktop token send screens in the Stack Wallet app. It is a straightforward user-interface fix that restores a feature already present on mobile and other send views; there is no indica…
This commit is purely a code-formatting cleanup. It changes line breaks and indentation in four user-interface files so the code is easier to read, but it does not change what the app actually does. There is no security relevance.
This commit fixes a UI bug in the desktop version of Stack Wallet where the send amount could be lost while the app was trying to estimate transaction fees. The fix keeps the amount 'alive' in memory so fee estimation does not accidentally…
State lifecycle issue in UI provider could lead to loss of user inputFix prevents fee estimation from silently resetting send amount to zeroNo cryptographic, authentication, or network security changes present
This commit updates the Stack Wallet app so that when a single payment is broken into multiple cryptocurrency transactions, the user sees a clear warning on the confirmation screen. It also changes the app's internal record-keeping to hand…
UI now warns users when a payment will be split into multiple on-chain transactionsInternal transaction model changed from single txid to list of txidsMultiple confirmation flows updated to iterate over all txids for notes and trade lookups
This commit fixes a performance bug in the desktop version of Stack Wallet where the app repeatedly re-fetched Bitcoin-style fee rates every time the on-screen fee form rebuilt. The change caches the fee result and only fetches again if th…
Unnecessary repeated network requests reducedFuture result cached to avoid re-execution on widget rebuildError path clears cache to allow retry
This commit fixes a UI state bug in Stack Wallet's send form. When a user clears the send form, the wallet now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old ad…
Stale UI state after form resetAddress validity not synchronized with address field resetPotential UI confusion leading to incorrect send confirmation
This is a large feature/fix merge that restores and rewrites the Xelis (XEL) cryptocurrency integration in Stack Wallet. It swaps the old hand-rolled Xelis code for a new generated native interface (XWF), adds wallet restore/backup support…
Send-flow lifecycle hardening: prepared Xelis transactions are now discarded via cancelSend when the user cancels or the widget is disposedSession-generation checks prevent stale wallet handles from being used after close/reopenMutex serialization added around send preparation, balance, history, and rescan operations
This commit is a large merge that mainly adds integration tests for a desktop 'forgot password' reset feature and makes supporting code changes to safely shut down background database workers during that reset. It also removes a large set …
New integration tests exercise a destructive 'forgot password' data-wipe featureTests assert that password store and wallet key store are deleted on successful resetTests assert that wallet files are deleted while backup and tor state are preserved
This commit lets users type multi-line notes when editing transaction and trade notes, and fixes the desktop layout so long notes scroll instead of breaking the screen. It also swaps the old `mounted` check for the newer `context.mounted` …
This commit is a large merge that mainly removes old integration tests and adds new desktop 'forgot password' reset tests. It also adds a safe-shutdown path for background Firo cache workers and databases. The changes look like defensive h…
Added safe shutdown of Firo cache isolates/SQLite databases before reset exitNew integration tests verify desktop forgot-password reset deletes secrets and preserves backupsTest harness intercepts exit() and IOOverrides to observe reset side effects
This commit fixes the desktop "forgot password" reset flow in Stack Wallet. It adds integration tests that verify the app can securely wipe its own data when a user forgets the desktop password, and it updates the Firo cache worker to clos…
Desktop password reset now closes Firo cache workers and SQLite databases before deleting app data, reducing the risk of data leakage or corruption during wipeNew integration tests assert that a successful reset removes password store (hive/desktopdata.hive), wallet key store (isar/desktopStore.isar), and wallet files while preserving backups and tor stateFailed reset scenario leaves a .reset-pending marker and removes password/key stores first, preventing the reset from being undone after partial deletion
This commit is a large merge that mainly adds a new 'prove you own a Spark address' feature to the Stack Wallet app, plus some related fixes. It also updates a dependency that handles SOCKS5 proxy connections and changes how the app decide…
New cryptographic signing path added: SparkInterface.signMessage now delegates to Spark ownership proof creation using the wallet's private key and spark derivation path.Ownership proof code rejects view-only wallets and blank messages, and searches a 100-address lookahead for the requested address before signing.Dependency upgrade: socks5_proxy 1.0.3+dev.3 -> 2.1.1, which may change SOCKS5/Tor proxy behavior; a new test verifies hostname/onion routing through a fake SOCKS server.
This commit adds a new feature to Stack Wallet that lets users prove they own a Spark (privacy) address by generating a cryptographic ownership proof. It also improves the sign/verify screens so view-only wallets can still verify proofs, a…
New cryptographic proof generation using private key material (privateKeyHex, spendKeyIndex, diversifier) inside an isolateView-only wallet guard added for proof creation (throws if isViewOnly)Message whitespace now preserved for pasted/typed challenge messages, preventing proof/verification mismatches caused by silent trimming
This commit merges several changes into a development branch. The most notable security-relevant change is a fix for how the Trocador exchange service routes traffic: it now automatically uses Tor (an anonymity network) when the user has T…
Trocador exchange API previously forced clearnet (`isOnion: false`) at every call site, bypassing Tor even when enabledNew `_useTor` getter centralizes Tor routing decision based on app feature flag and user preferenceOnion service address rotated to a new v3 .onion hostname
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedfix logical issueby julian · 2cdf6704 · Nov 5, 2025 · 1 fileMessage 28 · OpaqueLow 42Details
Commit message · julian
fix logical issue
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 42/100
This commit fixes a simple but important logic bug in a Dart helper class. The code was checking whether a function was null, but then doing the exact opposite of what it should: when the function existed, it did nothing; when it was missing, it tried to call the missing function and would have crashed. The fix flips the condition so the existing function is called and the alternative code path is used only when arguments are needed. The bug appears to be a plain coding mistake rather than a deliberate security flaw, but in a wallet app any crash or unexpected behavior during sensitive operations is worth treating carefully.
AI review queuedfix android SAF SWBby julian · 2bc27922 · Nov 5, 2025 · 6 filesMessage 28 · OpaqueLow 33Details
Commit message · julian
fix android SAF SWB
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 33/100
This commit changes how Stack Wallet's Android backup feature picks a save location. Instead of asking the user to choose a single file, it now asks the user to choose a folder. It also switches the auto-backup writer to use a helper that works with Android's Storage Access Framework (SAF), and it disables old-backup cleanup on Android because the SAF library cannot delete files. The change appears to be a bug fix for backups failing or misbehaving on Android due to file-path restrictions, not a fix for an active security vulnerability.
AI review queuedfix(spl): replace Ethereum-only transaction list with placeholderby sneurlax · fcd68bef · Nov 5, 2025 · 1 fileMessage 42 · ThinInformational 15Details
Commit message · sneurlax
fix(spl): replace Ethereum-only transaction list with placeholder
42/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a brand-new desktop screen for sending Solana SPL tokens. It is a UI placeholder/replacement for an Ethereum-only transaction list, not a security patch. There is no evidence in the commit message or diff of a vulnerability being fixed.
AI review queuedtry to ensure only one pop occursby Julian · dc1cca5c · Nov 5, 2025 · 4 filesMessage 57 · ThinLow 29Details
Commit message · Julian
try to ensure only one pop occurs
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100
This commit fixes a bug where scanning a QR code could accidentally close the same screen multiple times in rapid succession. The change wraps the scan handler so it only runs once, and also cancels the camera stream before closing the screen. Repeated pops could cause navigation glitches or minor app instability, but there is no direct evidence it could be used to steal funds or keys.
AI review queuedreplace mobile_scanner with an older library that does not use MLKit on androidby julian · 8ae4f2e0 · Nov 5, 2025 · 18 filesMessage 50 · ThinLow 40Details
Commit message · julian
replace mobile_scanner with an older library that does not use MLKit on android
50/100 · ThinMessage clarity
✓ Specific, 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 40/100
This commit swaps the app's QR code scanning library on Android from one that uses Google's ML Kit to an older one that does not. The change is framed as a privacy move to avoid sending camera frames to Google's ML services. The diff also adds null checks on scanned QR results, which prevents some crashes when a scan returns no content. There is no direct evidence in the commit that this fixes an active security vulnerability, and the bulk of the diff is formatting changes unrelated to security.
AI review queuedfeat(spl): add Solana token handling in wallet send/receive viewby sneurlax · 66da8bb3 · Nov 5, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat(spl): add Solana token handling in wallet send/receive view
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a placeholder UI message ('WIP') for sending Solana tokens on the desktop wallet view. It does not implement actual token-sending logic, nor does it change any security-sensitive code. The change is purely a UI stub to avoid falling through to the generic token-send widget for Solana wallets.
✓ 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 · Informational 19/100
This commit adds a user-facing toggle that lets Bitcoin wallet owners choose whether to generate older-style "legacy" (P2PKH) addresses. Previously, the app hid legacy addresses for Bitcoin wallets when other address types were available. The change is a feature addition, not a bug fix, and does not appear to address any security vulnerability.
AI review queuedfix(spl): handle missing Ethereum token wallet in shared componentsby sneurlax · c72c9c15 · Nov 5, 2025 · 3 filesMessage 62 · AdequateInformational 22Details
Commit message · sneurlax
fix(spl): handle missing Ethereum token wallet in shared components
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 22/100
This commit is a defensive bug-fix in the desktop wallet UI. It prevents the app from crashing when a Solana token wallet is selected, because the shared UI components were originally written only for Ethereum-style token wallets. The changes replace hard assumptions (that a token wallet always has an Ethereum contract object) with null checks, try/catch guards, and placeholder labels. There is no evidence of an exploitable vulnerability; it is a robustness improvement.
AI review queuedoptimize/cleanup electrumx_interface wallet addresses saved on recover/rescanby julian · dd67c858 · Nov 4, 2025 · 3 filesMessage 50 · ThinLow 31Details
Commit message · julian
optimize/cleanup electrumx_interface wallet addresses saved on recover/rescan
50/100 · ThinMessage clarity
✓ Specific, 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 31/100
This commit refactors how Stack Wallet saves wallet addresses during wallet recovery and rescanning for ElectrumX-based coins. It centralizes repeated address-gap-checking logic into a single helper function and changes how the highest used address index is tracked. The change appears intended to fix a bug where unused addresses beyond the gap limit could be incorrectly stored, which could lead to missing transactions or an incomplete wallet balance after restore. There is no clear evidence in the commit of a traditional security vulnerability such as theft of funds, but a bug in address discovery could affect wallet correctness and user funds visibility.
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Low 28/100
This commit adds a new 'Sign/Verify message' feature to Stack Wallet, letting users cryptographically sign messages with their wallet keys and verify signatures from others. It also corrects the message-prefix byte lengths for Dogecoin, Firo, and Namecoin so signatures match what other software expects. There is no clear security bug in the diff, but the signing code is new and touches private keys, so it deserves careful review.
feat(spl): register routes for Solana token (SPL) views
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfeat(spl): add Solana token selection in wallet token editorby sneurlax · 71178e68 · Nov 4, 2025 · 1 fileMessage 62 · AdequateInformational 14Details
Commit message · sneurlax
feat(spl): add Solana token selection in wallet token editor
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 14/100
This commit adds the ability for users to select and add Solana-based tokens (SPL tokens) inside the wallet's token editor. It is a feature addition that branches the existing Ethereum-only token flow to also support Solana wallets. There is no direct evidence in the commit that this fixes or introduces a security vulnerability; it is primarily a UI and data-handling change.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a new desktop screen for viewing Solana token (SPL) details in Stack Wallet. It is purely a user-interface feature with no security-sensitive code, no network calls, no cryptographic operations, and no changes to permissions or data handling. There is nothing in the diff that suggests a security vulnerability or fix.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit adds the ability for users to select Solana-based tokens (SPL tokens) in the Stack Wallet app. It is a feature implementation, not a security fix. The new code includes placeholder/stub functions that do not yet perform real Solana blockchain checks, and it adds debug logging that prints wallet addresses and selected token details during development. There is no direct evidence in the commit of a vulnerability being fixed or introduced.
AI review queuedfeat(spl): add Solana token storage and state mgmt providersby sneurlax · ba5492e3 · Nov 1, 2025 · 3 filesMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat(spl): add Solana token storage and state mgmt providers
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds new code to support Solana SPL tokens in Stack Wallet. It introduces a way to store token mint addresses in wallet metadata and two placeholder data providers for retrieving those addresses. The actual token detail fetching is left as a TODO and returns an empty list. There is no evidence of a security fix or vulnerability being addressed.
Lower-priorityfeat(spl): add Solana token (SPL) model and contract abstractionby sneurlax · e8327b6a · Nov 1, 2025 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · sneurlax
feat(spl): add Solana token (SPL) model and contract abstraction
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefeat(spl): flag/enable token support for Solanaby sneurlax · b9914576 · Oct 31, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · sneurlax
feat(spl): flag/enable token support for Solana
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit simply turns on a feature flag indicating that the Solana wallet now supports SPL tokens. There is no code change that fixes a bug, closes a security hole, or changes how funds are handled. It is a normal product feature enablement.