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…
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 16/100
This tiny commit reverts a database version bump and fixes a typo in a messaging refresh call. It appears to be a quick correction of an accidental change rather than a security fix. There is no clear security relevance visible in the code itself.
✓ 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 · Informational 15/100
This commit only updates automatically generated test mock files to match recent changes in the real code interfaces. It does not change any production code, user-facing behavior, or security-sensitive logic. The modifications adjust mock return types for a notification-index helper and add a mock for a new HTTP post-bytes method used in tests.
Security candidaterefactor notifications setup so we can add sib notifsby Julian · 16b90ff6 · Jul 11, 2026 · 19 filesMessage 50 · ThinInformational 19Details
Commit message · Julian
refactor notifications setup so we can add sib notifs
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 19/100
This commit is a feature refactor that adds a new in-app notification system for ShopInBit support tickets. It introduces a local database table for notifications, merges those notifications into the existing notification feed, and marks tickets/notifications as read when the user views them. There is no clear security vulnerability in the diff, but the change touches notification plumbing and local database migrations, so it carries normal implementation risk.
✓ Descriptive subject! 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 adds a new cryptocurrency exchange integration called CypherGoat to the Stack Wallet app. It lets users compare rates and create swaps through the CypherGoat service. The change is a normal feature addition, but it does introduce a new external API dependency and sends user-provided wallet addresses and trade details to api.cyphergoat.com. There is no direct evidence of a security vulnerability in the code itself, but any new third-party integration carries standard risks: the server could be compromised, the connection could be intercepted if certificate pinning is absent, or the API could return malicious data that the app might not fully validate.
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit only changes the marketing description text for a third-party concierge shopping service called ShopinBit. It rewords what users see on screen but does not alter any code behavior, security logic, or data handling.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 26/100
This commit adds the ability to attach files to customer-support messages in the ShopInBit feature of Stack Wallet. It introduces file picking, client-side type and size checks, and a multipart upload path to the server. The change is a feature addition, not a documented security fix. There are no obvious remote-code-execution or data-theft bugs visible in the diff, but the new code handles user-chosen files and uploads them over the network, which always carries some privacy and abuse risk.
Security candidatefix datetime sub second truncationby julian · b06e16d8 · Jul 10, 2026 · 3 filesMessage 45 · ThinInformational 20Details
Commit message · julian
fix datetime sub second truncation
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 20/100
This commit fixes how timestamps are stored for a built-in shopping/ticket feature. Previously, database columns used Drift's default dateTime type, which truncates fractional seconds. The patch switches those columns to store ISO 8601 UTC strings with millisecond precision and normalizes message timestamps to UTC. This is a data-integrity/correctness fix rather than a security vulnerability; it prevents subtle ordering or duplicate-detection bugs but does not create a direct path for an attacker to steal funds or run code.
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 16/100
This commit refines how the wallet app checks for updates to ShopInBit support tickets. It reduces unnecessary API calls by only fetching full ticket details and messages when something has actually changed, and it tightens the code so that newly created ticket records must always have complete data. There is no obvious security vulnerability here; it is primarily a performance and robustness improvement.
Security candidateShould continue polling while app is not the active/focused window on desktopby julian · 649cecf4 · Jul 10, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · julian
Should continue polling while app is not the active/focused window on desktop
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 18/100
This small change makes the app keep checking for updates on a 'ShopInBit ticket' page even when the desktop app window is not in focus. Previously, the app would pause polling when backgrounded and resume when the user returned. Now on desktop it never pauses. This is a behavior change, not a clear security fix or vulnerability. It could slightly increase background network activity and keep a connection alive longer, but there is no direct evidence it introduces a security flaw.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 18/100
This commit is a small code-quality cleanup in a cryptocurrency wallet app. It replaces a hardcoded text string ('NEW') and a hardcoded status value with references to a shared enum definition. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a maintainability improvement that reduces the chance of future typos or mismatched status values.
Security candidatehardcoded sib text logo colors to match previous icon styleby julian · 0142537c · Jul 9, 2026 · 6 filesMessage 50 · ThinInformational 15Details
Commit message · julian
hardcoded sib text logo colors to match previous icon style
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 15/100
This commit is a purely cosmetic UI change. It swaps the ShopinBit service icon from a generic settings-style icon to a dedicated 'SIB' logo, hard-coding the logo colors to match the previous style. It also removes a settings gear icon from the mobile services page. There is no security-relevant change visible in the diff.
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a routine UI cleanup of a travel-booking form inside the Stack Wallet app. It removes unused date-mode options (flexible dates, trip length, month/year pickers), simplifies the arrangement choices, reorders a text box, and changes one label to mention that users can paste a link. There is no security-relevant change visible in the code.
Security candidateget full ticket probably doesn't return different responses for the same id. Assuming this, we can safely poll status and messages more frequentlyby julian · 92b4dac9 · Jul 9, 2026 · 2 filesMessage 50 · ThinInformational 18Details
Commit message · julian
get full ticket probably doesn't return different responses for the same id. Assuming this, we can safely poll status and messages more frequently
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 18/100
This commit changes how often the app checks for updates on a support ticket and skips re-downloading the full ticket details when the app already has them. It is a routine performance and responsiveness improvement, not a security fix. There is no indication it addresses a vulnerability.
Security candidateSIB and GCs accessed from home screen on mobileby julian · f8dcdd8b · Jul 9, 2026 · 10 filesMessage 45 · ThinInformational 17Details
Commit message · julian
SIB and GCs accessed from home screen on mobile
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 17/100
This commit moves two existing app features—gift cards and concierge services—from a wallet-specific menu to the main home screen on mobile. It is a user-interface navigation change, not a security fix or vulnerability patch. There is no indication it fixes a bug that could be exploited.
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 17/100
This commit adds on-screen warnings telling users to send only USDT (TRC20) to a displayed address and not to send plain TRX. It is a user-interface safety hint, not a code change that fixes a software vulnerability. There is no evidence in the commit of an exploit, bug, or security flaw being patched.
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a purely cosmetic UI change. It adjusts the width and button height of a confirmation dialog on desktop versions of the app. There is no security relevance.
Security candidatesplit full name into separate fields for first and last nameby julian · d94c789f · Jul 8, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · julian
split full name into separate fields for first and last name
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 simply changes the user interface for entering a billing/shipping name. Instead of one 'Full name' text box that the app later tried to split into first and last names, it now shows two separate boxes labeled 'First name' and 'Last name'. There is no security fix or vulnerability here; it is a routine UI and data-handling refactor.
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 21/100
This commit fixes a programming crash in the Stack Wallet app's checkout screen. In some countries, the app was forcing a 'State' field to be shown even when no state was selected, which could cause the app to crash with a null error. The fix hides the state field when it isn't needed and only forces it when it is required.
Security candidateload offer before view/dialog opens so the accept button isn't disabled for a second or two without any info as to why displayedby julian · 5c94aa00 · Jul 8, 2026 · 2 filesMessage 62 · AdequateInformational 12Details
Commit message · julian
load offer before view/dialog opens so the accept button isn't disabled for a second or two without any info as to why displayed
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 12/100
This commit is a user-experience refactor, not a security fix. It moves the loading of a ShopInBit offer from inside the offer screen to the moment the user taps the 'Review offer' button, so the screen opens with data already loaded. The 'Accept offer' button no longer needs to be temporarily disabled while waiting. There is no indication this change addresses a security vulnerability.
✓ 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 simply renames a button label from 'Decline' to 'Cancel' on a shopping offer screen so the text matches what the button actually does (close the screen). There is no security relevance.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 16/100
This is a small code-quality cleanup in a Flutter screen that shows ticket attachment details. It stops passing a UI framework reference (WidgetRef) into helper methods and instead passes the actual service object directly. There is no direct security vulnerability visible in the diff, but the change removes a pattern that can make code harder to reason about and could theoretically hide lifecycle bugs.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This is a small bug-fix patch in a mobile wallet's shopping-support ticket screen. It stores a service reference when the screen first loads, then reuses that reference later, instead of asking the app's state-management system for the service again after the screen may have been destroyed. The change prevents a runtime crash ('provider read after dispose') but does not appear to be a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 18/100
This is a one-line UI bug fix for opening attachment links on desktop versions of the Stack Wallet app. The change tells the app to use the root navigator on desktop when displaying an 'Opening attachment' progress indicator. There is no indication this fixes a security vulnerability; it appears to address a navigation/display issue specific to desktop layouts.
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a minor user-interface wording cleanup for a shopping feature. It changes two on-screen labels so that the heading now mentions VAT and the price line no longer repeats it. There is no security relevance in the code change itself.
Security candidateshorten and clarify concierge main request text fieldby julian · 90e9bb96 · Jul 8, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · julian
shorten and clarify concierge main request text field
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 changes a user-visible label in a shopping concierge form from a longer description to a shorter one, and tweaks how a multi-line text field label is visually aligned. There is no security-relevant change.