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.
52/100 average clarity
61Strong · 80–100
359Adequate · 60–79
549Thin · 40–59
197Opaque · 0–39
33security candidates with opaque commit messaging
This commit fixes a bug in how Taproot (a modern Bitcoin-style transaction format) inputs were being built. Previously, the 'sequence number'—a field that controls things like time-locks and replacement rules—was being dropped for Taproot …
Missing nSequence preservation for Taproot key-path inputsBehavioral divergence between Taproot and other input types in the same switchPotential for unintended transaction semantics (RBF, timelocks) due to default sequence value
This commit changes how Stack Wallet picks and updates Bitcoin receiving addresses. It makes the wallet rotate (advance to a fresh address) not just on its main address type, but also on other supported address types when they have transac…
Address rotation logic added for non-main derivation pathsView-only Taproot wallet explicitly rejected in Buy flow to avoid deriving addresses without private key materialNew test coverage for address reuse and rotation across BIP44/BIP84/BIP86 paths
This change fixes how Stack Wallet picks a Bitcoin receiving address when a user buys crypto through Simplex. Previously, the app could generate a fresh address every time instead of reusing the same one, which could cause funds sent to an…
Address reuse / derivation index stability for fiat-to-crypto buy flowRace-condition protection via mutex for address generationRemoval of direct Isar query from UI layer in favor of wallet abstraction
This commit adds automated integration and widget tests for the 'Buy' form's 'Choose from Stack' feature in a cryptocurrency wallet app. It does not change production code, fix bugs, or alter security behavior. It only verifies that the ex…
This commit fixes a privacy and usability bug in Stack Wallet. Previously, when the wallet refreshed its transaction history, it only checked whether the main receiving address (for example, a Taproot address) had been used. If you had gen…
This update fixes how Stack Wallet detects Bitcoin transactions that have disappeared from the memory pool (unconfirmed transactions). Previously, the wallet only recognized a specific error message format used by some server software. Now…
Error-handling robustness improvementData consistency fix for local transaction databaseServer-backend compatibility broadening
This is a large build-system refactor for a cryptocurrency wallet app. It replaces an older manual native-library build process with a new 'dnix' system that can either build libraries from source or download verified prebuilt binaries. Th…
Build system refactor only: no application runtime code changedNew verification step check_native_overrides.dart added to CI and local configure flowPrebuilt binaries are now verified against package dnix.lock hashes instead of app-level manifest URLs
This is a large merge commit that rewrites how the wallet connects to Electrum servers. The main security-relevant changes are: each wallet now owns its own Electrum connection instead of sharing one global client; the app learns to rememb…
Per-wallet Electrum connection ownership replaces shared singleton, reducing cross-wallet state contaminationTrusted TLS certificate pinning per node (host/port/SSL) addedCertificate approval UI with SHA-256 fingerprint display and forget action
This is a large refactor of how the Stack Wallet app connects to Electrum servers. Previously, all wallets of the same coin shared one global Electrum connection, which could leak wallet activity across wallets and made it hard to cleanly …
Shared Electrum client manager removed; per-wallet client isolation addedTLS certificate pinning/trust-on-first-use support added for Electrum nodesPer-request timeouts added instead of single global timeout
This commit only rewords comments and a test name. It changes the phrase 'approval pins the certificate' to 'approval accepts the certificate' and clarifies that only untrusted certificates reach the custom check. There is no code behavior…
This commit is purely a code-formatting cleanup in a single Dart file. It rewraps a few lines of navigation and theme code to match the project's style guide. There are no functional changes, no bug fixes, and no security relevance.
This is a large merge commit that refactors how transaction fees are calculated and displayed across Stack Wallet's send screens. It replaces duplicated fee-calculation code in many send views with a shared set of providers and helper widg…
Refactor of transaction-fee estimation logic across send flowsRemoval of duplicated fee-calculation code and session cachesIntroduction of shared fee providers and reusable UI helpers
This is a large code refactor that moves fee-calculation logic out of individual send screens into shared providers and helper classes. The goal is to make the send fee UI behave consistently across mobile, desktop, token, and Solana token…
Refactor of transaction fee estimation and selection UI across all send flowsConsolidation of wallet-specific fee logic (Cryptonote priorities, Firo Spark/public/OP_RETURN, Solana token fallback, Ethereum custom EIP-1559) into shared providersRemoval of per-view fee caches and timers; replacement with shared debounce/focus-loss retry logic
This commit adds a new feature to Stack Wallet that lets Monero (XMR) users cryptographically sign messages with their wallet address and verify signatures from others. It is a routine feature addition, not a security fix or vulnerability …
This commit adds a new feature to Stack Wallet that lets Monero wallet users cryptographically sign messages with their wallet keys and verify signatures from others. It is a routine feature implementation, not a security fix. There is no …
Feature addition, not a patch or fixView-only wallets are explicitly blocked from signingEmpty signature result from underlying library is treated as failure
This commit fixes a bug where Stack Wallet could not clean up old unconfirmed transactions when connected to electrs servers. The wallet checks whether a transaction still exists on the server; it previously only recognized ElectrumX/Fulcr…
Error-message parsing used for transaction lifecycle decisionWallet state desynchronization due to backend-specific error handlingRBF/replaced transaction cleanup failure
This commit fixes a user-interface bug in Stack Wallet's Solana token-add flow. Previously, when a user created a new Solana wallet while trying to add a Solana token, the wallet picker could see the newly created wallet in the database be…
No cryptographic or signing code changedNo network or RPC behavior changedNo authentication, authorization, or permission logic changed
This commit fixes a UI crash in Stack Wallet that could occur when adding an Ethereum token right after creating a new Ethereum wallet. The problem was a timing mismatch: the new wallet's basic info was saved to the database before the wal…
Crash/DoS in wallet picker UI due to inconsistent wallet registration stateRace condition between database persistence and in-memory provider registrationUI state derived from one provider (all wallet info) without checking another provider (registered wallets)
This commit only reformats Dart code to match the project's current Dart SDK style rules. It changes whitespace, line breaks, and import grouping in two wallet-related UI files. There are no functional changes, no security fixes, and no be…
This commit fixes a UI bug in Stack Wallet's Ethereum token-add flow. During wallet creation, the app briefly knew about a new Ethereum wallet before the wallet was fully registered, causing the token picker to show an empty or broken list…
fix: point Dogecoin and Litecoin default explorer links at sochain.com
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 23/100
This commit simply updates the default web links used to view Dogecoin and Litecoin transactions. The old links pointed to chain.so, which now redirects to sochain.com; the new links go directly to sochain.com. There is no code vulnerability or user-data risk visible in the change itself.
Lower-priorityFix executable-stack flags in Linux CI bundles before packagingby Dan Miller · 02b5b0ab · Oct 25, 2026 · 6 filesMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Fix executable-stack flags in Linux CI bundles before packaging
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatefix: point Dogecoin and Litecoin default explorer links at sochain.comby Atif Nazir · 4642939c · Oct 24, 2026 · 2 filesMessage 85 · StrongInformational 17Details
Commit message · Atif Nazir
fix: point Dogecoin and Litecoin default explorer links at sochain.com
chain.so explorer links now reach the transaction page only after two redirects (chain.so/tx/DOGE/<txid> -> sochain.com/tx/DOGE/<txid> -> sochain.com/doge/tx/<txid>). Use the current form directly for mainnet and testnet.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 17/100
This commit simply updates the default web links used to look up Dogecoin and Litecoin transactions. The old chain.so URLs now redirect twice before showing the transaction, so the developer pointed the wallet directly at the new sochain.com address format. It is a routine maintenance change to keep the 'View on block explorer' feature working smoothly.
✓ 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 pathboot or update path
AI analysis · Informational 15/100
This commit is a large batch of new and updated automated tests for the send-money screens in Stack Wallet. It checks that fee estimates are displayed correctly, that users can pick custom fees, and that fees update when balances or sync status change. There are no changes to the actual wallet app code that users run—only test code.
Lower-priorityMerge pull request #1474 from cypherstack/ios-27-required-changesby Julian · 7ce7b34f · Oct 19, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Julian
Merge pull request #1474 from cypherstack/ios-27-required-changes
UIScene related changes required by flutter for ios 27
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-priorityUIScene related changes required by flutter for ios 27by Julian · 8185f054 · Oct 19, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Julian
UIScene related changes required by flutter for ios 27
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidaterefactor: share the send fee logic across platformsby Cyrix126 · f9ec2c3e · Oct 16, 2026 · 24 filesMessage 62 · AdequateInformational 11Details
Commit message · Cyrix126
refactor: share the send fee logic across platforms
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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 11/100
This commit is a code cleanup that moves fee-calculation logic out of several send screens into a single shared module. It does not change what the app does; it only reorganizes how fee estimates are computed and displayed across mobile and desktop. There is no indication this introduces a security vulnerability.
multi recipient monero uri semi colon parsing tweak
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedmulti recipient ui fixesby Julian · 0b8c3f39 · Oct 13, 2026 · 8 filesMessage 28 · OpaqueLow 40Details
Commit message · Julian
multi recipient ui fixes
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 40/100
This commit fixes UI bugs in Stack Wallet's multi-recipient send screen. The changes make payment-request names display more safely (so a malicious name can't be confused with a trusted contact label), ensure payment-request messages are actually used, and add several 'mounted' checks to prevent crashes when a user navigates away during QR scanning or clipboard access. The patch is defensive and improves security posture, but it is a partial UI fix rather than a complete elimination of all related risks.
AI review queuedMerge pull request #1459 from waozixyz/monero-multi-recipient-uriby Julian · 83bb15f8 · Oct 13, 2026 · 12 filesMessage 73 · AdequateLow 32Details
Commit message · Julian
Merge pull request #1459 from waozixyz/monero-multi-recipient-uri
Support multi-recipient Monero payment URIs
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 32/100
This commit adds support for Monero payment links that can specify multiple recipients at once, such as splitting a bill. It updates the wallet's send screen, confirmation screen, and address parsing logic so users can scan or paste a single Monero URI and pay several addresses in one transaction. The change is a feature addition, not a bug fix, and the code includes validation and tests for malformed URIs.
Merge pull request #1469 from Cyrix126/building_dialog_cancel
fix: mobile, canceling a transaction build closes an extra view
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Informational 24/100
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 error dialogs from appearing after the user has already cancelled. It is a user-experience bug fix, not a security vulnerability.
AI review queuedMerge branch 'staging' into building_dialog_cancelby Julian · 0485b166 · Oct 8, 2026 · 6 filesMessage 50 · ThinInformational 20Details
Commit message · Julian
Merge branch 'staging' into building_dialog_cancel
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
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, making desktop fee estimates fetch only once (and retry after a failure), and adding QR-code scan buttons to two desktop token send pages. There is no direct evidence in the commit that these were security vulnerabilities, and the commit message does not describe security relevance.
AI review queuedMerge pull request #1468 from Cyrix126/desktop_fee_form_refetchby Julian · 62432946 · Oct 8, 2026 · 2 filesMessage 58 · ThinInformational 17Details
Commit message · Julian
Merge pull request #1468 from Cyrix126/desktop_fee_form_refetch
Desktop fee form refetch
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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100
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 fetch failed. There is no indication this is a security fix.
AI review queuedMerge branch 'staging' into desktop_fee_form_refetchby Julian · 8a72c82f · Oct 8, 2026 · 4 filesMessage 50 · ThinInformational 17Details
Commit message · Julian
Merge branch 'staging' into desktop_fee_form_refetch
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100
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 no direct evidence in the commit that these changes fix a security vulnerability; they appear to be normal UI/UX improvements and state cleanup.
AI review queuedMerge pull request #1467 from Cyrix126/clear_send_form_validityby Julian · d3383b4e · Oct 8, 2026 · 2 filesMessage 73 · AdequateLow 32Details
Commit message · Julian
Merge pull request #1467 from Cyrix126/clear_send_form_validity
fix: reset the address validity when clearing the send form
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 32/100
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 an old address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is acceptable. There is no direct evidence in the commit of funds being stolen or a remote attack.
AI review queuedMerge branch 'staging' into clear_send_form_validityby Julian · 22560a59 · Oct 8, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Julian
Merge branch 'staging' into clear_send_form_validity
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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.
AI review queuedMerge pull request #1466 from Cyrix126/desktop_token_qr_buttonby Julian · 47f6d369 · Oct 8, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · Julian
Merge pull request #1466 from Cyrix126/desktop_token_qr_button
fix: add missing QR scan button to desktop token send views
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
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 indication it fixes a security vulnerability.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
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.
AI review queuedstyle: formattingby Cyrix126 · 09ed5441 · Oct 8, 2026 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Cyrix126
style: formatting
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit contains only cosmetic code formatting changes—adjusting line breaks and indentation in four files. There are no functional changes, no bug fixes, and no security-related modifications.
AI review queuedfix: stop estimating the desktop fee for a zero amountby Cyrix126 · 90c91bde · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · Cyrix126
fix: stop estimating the desktop fee for a zero amount
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 23/100
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 reset it to zero. There is no direct evidence this is a security vulnerability, but it could cause user confusion or failed transactions.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 32/100
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 handle multiple transaction IDs (txids) instead of assuming there is always just one. The main risk being addressed is that a user might accidentally send a split payment to a vendor or exchange that only credits single-transaction payments, leading to lost or miscredited funds.
AI review queuedfix: stop refetching the desktop fee rates on every rebuildby Cyrix126 · a1ca9292 · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 18Details
Commit message · Cyrix126
fix: stop refetching the desktop fee rates on every rebuild
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 18/100
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 the previous attempt failed. It is primarily a reliability/efficiency improvement, not a security fix.
AI review queuedfix: reset the address validity when clearing the send formby Cyrix126 · 43dd0477 · Oct 6, 2026 · 2 filesMessage 62 · AdequateLow 34Details
Commit message · Cyrix126
fix: reset the address validity when clearing the send form
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 · Low 34/100
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 address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is ready to send to.
Merge pull request #1450 from Ez3kiel-dev/fix/xelis-integration
fix(xelis): restore wallet integration with XWF
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 35/100
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, improves send-flow safety by cancelling prepared transactions when the user leaves the confirmation screen, and adds many integration tests. There is no direct evidence in the commit of an active security vulnerability being patched; the changes look like a substantial integration repair with several defensive-hardening improvements.