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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit cleans up a merge conflict in the Stack Wallet app. It adds a new optional database column to store the raw order status text from a third-party shopping service (ShopInBit), updates the generated database code, and fixes a small logic bug where an order status could be set to null. There is no obvious security vulnerability here; it looks like a routine data-model and bug-fix cleanup after merging two branches.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefix(ui): More shopinbit stuff, navigation fixes, styling, etc etc. Probably still a WIPby julian · 28f495cf · May 25, 2026 · 8 filesMessage 42 · ThinInformational 18Details
Commit message · julian
fix(ui): More shopinbit stuff, navigation fixes, styling, etc etc. Probably still a WIP
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
authentication path
AI analysis · Informational 18/100
This commit is a routine user-interface refactor for a third-party shopping feature called ShopinBit. It replaces some desktop-specific popup dialog code with a shared navigation system, tweaks button layouts, and fixes styling. There is no clear security bug being patched, and no sensitive data handling or cryptographic code is changed.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit changes a single user-interface label in a travel booking form. The dropdown that previously showed the placeholder text 'Month or season' now shows just 'Month'. There is no security relevance: it is purely a wording correction.
Security candidateuse date picker widget in shopinbit formby julian · bb4ca156 · May 23, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · julian
use date picker widget in shopinbit form
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit replaces two separate date text fields in a travel booking form with a single built-in date-range picker widget. It is a routine user-interface cleanup with no apparent security relevance.
AI review queuedfeat(ui): extract date picker widgetby julian · 0376406d · May 23, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · julian
feat(ui): extract date picker widget
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine user-interface cleanup: it moves the date-range picker code out of the transaction-search screen and into a reusable widget file. There is no security-relevant change visible in the diff.
Security candidatefeat(ui): date picker range selectionby julian · 491d6d6a · May 23, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · julian
feat(ui): date picker range selection
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
signing or wallet pathauthentication path
AI analysis · Informational 15/100
This commit is a routine user-interface feature update. It extends the app's custom date picker so it can optionally return a date range instead of a single date, and updates the existing call sites to keep using only the first selected date. There is no security-relevant change visible in the diff.
Security candidatefix(ui): date picker styleby julian · 8493d129 · May 23, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · julian
fix(ui): date picker style
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
authentication path
AI analysis · Informational 15/100
This commit is a routine user-interface styling fix. It swaps the standard Flutter date picker for a custom Stack Wallet date picker in a travel booking form and makes the custom picker accept optional start/end date limits. There is no security-relevant change visible in the code.
Security candidatetweak mobile layout to make checkboxes look betterby julian · c97aa979 · May 23, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · julian
tweak mobile layout to make checkboxes look better
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit only adjusts vertical spacing (padding) between checkboxes and buttons on mobile screens in three shopping/concierge forms. It is a cosmetic UI tweak with no security relevance.
Lower-priorityfix(ui): Use existing refresh arrows animationby julian · 1a7976a8 · May 23, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · julian
fix(ui): Use existing refresh arrows animation
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix: resize campfire icon to 512x512by Dan Miller · 620ccce8 · May 23, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Dan Miller
fix: resize campfire icon to 512x512
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(ci): install cargo-lipo for stack_duo macOS buildby Dan Miller · 05d4fabe · May 23, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Dan Miller
fix(ci): install cargo-lipo for stack_duo macOS build
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix: resize campfire icon to 512x512, revert flatpak CI workaroundby Dan Miller · ab31e9c2 · May 22, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Dan Miller
fix: resize campfire icon to 512x512, revert flatpak CI workaround
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
fix(ui): prevent squared textfield bottom corners when error message displayed
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: upgrade actions to latest major versions (setup-go v6, upload/download-artifact v7/v8, cache v5)by Dan Miller · a31e0945 · May 22, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Dan Miller
ci: upgrade actions to latest major versions (setup-go v6, upload/download-artifact v7/v8, cache v5)
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
documentation-only discount
Lower-priorityci: fix Rust toolchains and campfire flatpak icon for non-linux buildsby Dan Miller · ae2fabe0 · May 22, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Dan Miller
ci: fix Rust toolchains and campfire flatpak icon for non-linux builds
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
documentation-only discount
Security candidatefix(ui): only show close warning dialog when appropriateby julian · 09bf8ce2 · May 22, 2026 · 6 filesMessage 62 · AdequateInformational 18Details
Commit message · julian
fix(ui): only show close warning dialog when appropriate
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
authentication path
AI analysis · Informational 18/100
This commit fixes a user-interface annoyance in Stack Wallet. Previously, closing certain pop-up dialogs would show an unnecessary 'are you sure you want to close?' warning even when no important progress was at risk. The change makes the warning appear only when appropriate, such as when the user is in the middle of a multi-step flow, and skips it on the very first step or when the navigation stack is empty. There is no direct evidence this is a security fix.
AI review queuedci: add AppImage builds and full platform coverage for campfire and stack_duoby Dan Miller · b37c4655 · May 22, 2026 · 15 filesMessage 72 · AdequateInformational 15Details
Commit message · Dan Miller
ci: add AppImage builds and full platform coverage for campfire and stack_duo
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds new build and packaging automation. It creates GitHub Actions jobs to produce AppImage, Flatpak, Android, Windows, macOS, and iOS builds for the Campfire and Stack Duo wallet variants, plus small launcher scripts and desktop metadata files. There is no change to wallet logic, cryptography, networking, or user data handling.
Security candidatefeat(ui): allow custom nested nav flow close argsby julian · 8413a3dd · May 22, 2026 · 6 filesMessage 57 · ThinInformational 12Details
Commit message · julian
feat(ui): allow custom nested nav flow close args
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
authentication path
AI analysis · Informational 12/100
This commit is a user-interface cleanup. It moves the 'Are you sure you want to close?' confirmation logic into a shared dialog widget and lets different screens choose whether to show a warning, a generic message, or no warning at all. There is no indication this fixes a security vulnerability; it appears to be a normal feature/refactoring change.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a routine user-interface cleanup for the ShopinBit checkout flow. It swaps one dialog widget for another, adjusts spacing and padding, replaces a Material icon with an SVG icon, removes an unused internal warning dialog, and tweaks dropdown positioning. There is no indication of any security fix or behavior change that would affect user safety.
Lower-priorityci: embed Flathub runtime-repo in flatpak bundleby Dan Miller · d5fd1489 · May 22, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Dan Miller
ci: embed Flathub runtime-repo in flatpak bundle
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
documentation-only discount
AI review queuedAdd flatpak build job to CIby Dan Miller · c457649f · May 22, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Dan Miller
Add flatpak build job to CI
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 · Informational 15/100
This commit adds a new automated build step that produces a Flatpak installer for Linux. It does not change the wallet's code, cryptographic handling, or permissions beyond what a normal Linux desktop app needs. There is no indication this is a security fix or introduces a vulnerability.
AI review queuedflatpak: grant filesystem access to ~/.stackwalletby Dan Miller · 94168a9b · May 22, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Dan Miller
flatpak: grant filesystem access to ~/.stackwallet
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 26/100
This commit changes the Flatpak packaging for Stack Wallet so the app can read and write files in a folder named .stackwallet inside the user's home directory. Flatpak apps normally run in a sandbox with limited access to the rest of the system. The change gives the app access to one specific, named folder, which is a common and usually reasonable way for a wallet app to store its data. By itself, this is not a vulnerability, but it slightly widens the sandbox. If the app were ever compromised, that folder could be read or modified by the attacker.