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…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedupdate mobile_app_privacy with swiftpmby Julian · 03ad8804 · Sep 16, 2026 · 2 filesMessage 35 · OpaqueLow 30Details
Commit message · Julian
update mobile_app_privacy with swiftpm
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 30/100
This commit updates a dependency called mobile_app_privacy from version 0.0.3 to a specific commit hash (0.0.4). The change appears to be a routine dependency bump to incorporate Swift Package Manager support, but the commit message gives almost no detail. Without seeing what actually changed inside the mobile_app_privacy library, we cannot tell whether this fixes a security issue, introduces one, or is purely a build/dependency change.
Security candidateformatting to make ci happyby Julian · bef9da69 · Sep 16, 2026 · 55 filesMessage 45 · ThinInformational 15Details
Commit message · Julian
formatting to make ci happy
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathauthentication path
AI analysis · Informational 15/100
This commit is purely a code-formatting cleanup. It changes whitespace, line breaks, and indentation across many Dart files so the project's automated style checks (CI) pass. No program logic, security behavior, or user-facing functionality was altered.
AI review queuedios/xcode auto updatedby Julian · 712bd226 · Sep 16, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Julian
ios/xcode auto updated
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit changes only the recorded dimensions of the iOS launch screen image in a storyboard file, from 512×373 to 512×512. It is a routine Xcode/auto-update style tweak with no visible security relevance.
AI review queuedupdate deps and generated files to make the machines happyby Julian · 6988214e · Sep 15, 2026 · 26 filesMessage 50 · ThinInformational 17Details
Commit message · Julian
update deps and generated files to make the machines happy
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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit updates several software building blocks (dependencies) and the automatically generated code that matches them. The main change is moving the Isar database library from a pre-release test version (3.3.0-dev.2) to a stable release (3.3.2), along with related tools like build_runner, analyzer, hive_ce, and mockito. It also removes a workaround that pinned an older analyzer version. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as routine maintenance to keep the project compatible with newer tooling.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 14/100
This commit updates the Stack Wallet app to use a newer version of its Tor privacy plugin and switches to prebuilt native assets downloaded from GitHub. There is no direct evidence in the commit of a security vulnerability, but changing how sensitive privacy components are fetched and built is a security-relevant configuration change.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 17/100
This commit updates dependency versions for Xelis cryptocurrency support in Stack Wallet. It switches from the upstream xelis-flutter-ffi library to a fork maintained by Cypher Stack (the same organization as the wallet), and bumps flutter_rust_bridge from 2.12.0 to 2.13.0. The commit title says 'xelis native assets,' suggesting feature work rather than a security fix. There is no direct evidence in the diff or commit message of a vulnerability or security issue.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100
This commit simply updates the version of an external library called 'epiccash' used by the Stack Wallet app. It changes which exact code snapshot and prebuilt download the app will use, but the commit message gives no details about why the update was made or whether it fixes any security problem. Without seeing the actual changes inside the epiccash library, we cannot tell if this is a routine update or a security patch.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 6/100
This commit simply updates the version of an internal backup library (stack_wallet_backup) used by the Stack Wallet app. The change points the app to a newer commit of that library and bumps its declared version from 0.0.1 to 0.1.0. There is no information in the commit itself about what changed in the backup library or whether any of those changes relate to security.
AI review queuedDoes what https://github.com/cypherstack/stack_wallet/pull/1442/ intended but without the negative side effectsby Julian · 04694bc5 · Sep 15, 2026 · 2 filesMessage 58 · ThinInformational 19Details
Commit message · Julian
Does what https://github.com/cypherstack/stack_wallet/pull/1442/ intended but without the negative side effects
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 pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit adjusts two on-screen selection sheets in the Stack Wallet mobile app so they respect the phone's safe area (notch, gesture bar, etc.) and fixes some padding. It also removes a duplicate spacer in one sheet. There is no indication this fixes a security vulnerability; it appears to be a UI/UX follow-up to an earlier pull request.
AI review queuedclean up build scriptsby Julian · 5cfeb9b9 · Sep 15, 2026 · 22 filesMessage 28 · OpaqueInformational 15Details
Commit message · Julian
clean up build scripts
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit is a routine cleanup of build scripts. It removes old shell scripts that manually compiled cryptocurrency plugin libraries and updates the build instructions to rely on Flutter's newer native-assets system. There is no indication of a security fix, vulnerability, or malicious change.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 3/100
This commit simply updates a dependency reference for libmwc (a Mimblewimble Coin library) from one Git commit hash to another. There is no description of what changed in the library, no mention of security fixes, and no diff showing actual code changes in Stack Wallet itself. On its own, this commit does not demonstrate any security issue.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 25/100
This commit changes how the Stack Wallet app pulls in its Epic Cash cryptocurrency library. Previously, the library was included as a local Git submodule inside the project. Now, the app fetches it directly from a specific Git commit on GitHub as a 'native asset' dependency. The commit also removes the user-facing display of the Epic Cash build commit hash from the About screen and deletes the code that checked whether that commit was the latest one. This is primarily a build-system and UI cleanup change; there is no direct evidence in the diff of a security vulnerability being fixed.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit changes how the app pulls in a supporting cryptography library called frostdart. Previously it was included as a local submodule; now it is fetched directly from its GitHub repository at a specific commit. There is nothing in the commit that fixes, introduces, or discusses a security vulnerability. It is a routine build/dependency plumbing change.
Security candidatemwc native assets package migration (removes need for submodule and fixes issue on macos)by Julian · 2509dd9e · Sep 11, 2026 · 11 filesMessage 50 · ThinInformational 18Details
Commit message · Julian
mwc native assets package migration (removes need for submodule and fixes issue on macos)
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 18/100
This commit changes how the Mimblewimblecoin (MWC) crypto library is bundled in the Stack Wallet app. It removes the old Git submodule setup and instead pulls the library directly from a specific Git commit. It also re-enables MWC support on macOS and removes some on-screen build-commit information for MWC. There is no obvious security vulnerability in the diff itself, but the change shifts trust to a pinned external Git reference and removes a visible transparency check.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 35/100
This commit updates the SQLite-related Dart/Flutter packages used by the Stack Wallet app. It bumps versions of the database library (drift), the underlying SQLite bindings (sqlite3), and related tooling. The change also removes the direct dependency on sqlite3_flutter_libs and adds sqlcipher_flutter_libs as a transitive dependency. The commit message gives no reason for the update, so we cannot tell from the diff alone whether it fixes a security bug, a compatibility issue, or something else. Updating dependencies is a routine maintenance action, but because this touches the encrypted local database layer of a cryptocurrency wallet, any underlying vulnerability could have high impact.
flutter 3.47 and dart 3.13 minimum and associated changes
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 18/100
This commit updates the Stack Wallet app to require newer Flutter and Dart versions. Most changes are routine housekeeping: reformatting code, removing the 'final' keyword from function parameters to match new language rules, updating iOS/macOS build files, and bumping dependency versions. There are a few small logic tweaks, such as adding null-assertions ('!') to some wallet scanning code and changing how the app detects iPads, but nothing in the diff clearly introduces or fixes a security vulnerability.
AI review queuedfix test importby Julian · 97cfbd96 · Sep 4, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Julian
fix test import
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! 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 is a one-line fix in a test file that updates an import path from an old package name ('paymint') to the current package name ('stackwallet'). It does not change any production code, user-facing behavior, or security logic. It simply allows a unit test to compile and run correctly.
✓ 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 28/100
This commit updates the Stack Wallet app so it can correctly identify a newer kind of Firo cryptocurrency transaction (Spark V2 spends). Previously, the wallet only recognized one transaction type as a Spark spend; now it also recognizes type 11. This is a small correctness fix that helps the wallet display balances and transaction history accurately for Firo users. There is no direct evidence in the commit that this is a security vulnerability or that it was exploited.
✓ 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 23/100
This commit updates the Stack Wallet app so it can correctly identify a newer kind of Firo cryptocurrency transaction (Spark V2 spends, type 11) in addition to the older Spark V1 spends (type 9). Before this change, the wallet only recognized type 9 as a spend, so a type-11 spend might have been misclassified or mishandled in the user's transaction history and balance calculations. There is no direct evidence in the commit that this misclassification could be exploited by an attacker to steal funds, but it is a correctness fix that could affect balance display and user trust.
AI review queuedfix send to spark name gray screen (nav error)by Julian · 04ee6496 · Sep 1, 2026 · 1 fileMessage 45 · ThinInformational 20Details
Commit message · Julian
fix send to spark name gray screen (nav error)
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 20/100
This commit fixes a UI crash (gray screen) that occurred when confirming a transaction sent to a Spark name. The crash happened because the code tried to read the first recipient address from an empty list. The fix safely checks whether a recipient exists before reading its address, falling back to Spark-specific recipient data when needed. There is no indication this is a security vulnerability; it is a robustness fix for a user-facing navigation/display error.
AI review queuedpartial revert of SIST in prep for h2 forkby Julian · 27d00b05 · Sep 1, 2026 · 9 filesMessage 45 · ThinLow 31Details
Commit message · Julian
partial revert of SIST in prep for h2 fork
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 31/100
This commit re-enables sending private Firo (Spark) funds to exchange addresses, which had been temporarily blocked. It also upgrades the wallet to support a newer Spark transaction format (Chaum V2) that allows multiple inputs, and it adds safety checks to prevent broadcasting insecure multi-input transactions using the older format. The change is described by the developer as a 'partial revert' ahead of a network fork, not as a security fix.
AI review queuedflutter_libsparkmobile dependency updateby Julian · d458a426 · Aug 31, 2026 · 6 filesMessage 35 · OpaqueInformational 23Details
Commit message · Julian
flutter_libsparkmobile dependency update
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit updates the Stack Wallet app's integration with the Firo Spark privacy library. It adds support for a new Spark transaction version ("H2" / Chaum V2) that activates on mainnet at block 1,371,000, while keeping older behavior on test networks. The change is a dependency and protocol upgrade, not a clear security fix, but it touches sensitive code that creates private transactions and could affect whether coins are spendable after the network upgrade.
AI review queuedupdate windows mwebdby Julian · abbe566a · Aug 28, 2026 · 3 filesMessage 28 · OpaqueInformational 24Details
Commit message · Julian
update windows mwebd
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 24/100
This commit updates the Windows build pipeline for a small helper program called mwebd, which Stack Wallet uses for Litecoin MWEB privacy features. It bumps the mwebd version from v0.1.8 to v0.1.19, switches to a newer Go compiler, removes an old workaround that disabled part of the upstream plugin, and fixes a checksum comparison bug caused by Windows file paths. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies and removing workarounds can have security side effects.
AI review queuedci test image goby Julian · c2443f27 · Aug 28, 2026 · 1 fileMessage 38 · OpaqueInformational 21Details
Commit message · Julian
ci test image go
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 21/100
This commit updates the project's Docker build image to install the Go programming language toolchain. It downloads Go 1.24.13 from the official Go website, verifies the file's integrity using a published SHA-256 checksum, extracts it, and adds it to the container's system PATH. The change appears to be a routine CI/build environment update rather than a security fix or vulnerability patch. There is no direct evidence in the commit that this addresses a security issue.
AI review queuedupdate mweb fee logicby Julian · d70c03d4 · Aug 28, 2026 · 4 filesMessage 28 · OpaqueLow 32Details
Commit message · Julian
update mweb fee logic
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 32/100
This commit rewrites how Stack Wallet calculates fees for MWEB (a privacy feature in Litecoin). It introduces a new helper module that reconciles the estimated fee against what the transaction actually pays, and loops up to 10 times to fix mismatches. The change appears to be a bug-fix/refactor of fee arithmetic rather than a new feature or an obvious security patch. There is no vendor statement that this fixes a security vulnerability.