Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
51/100 average clarity
33Strong · 80–100
316Adequate · 60–79
513Thin · 40–59
191Opaque · 0–39
33security candidates with opaque commit messaging
This commit fixes a mobile UI bug where pressing Cancel on a 'building transaction' dialog accidentally closed one too many screens. The fix moves the responsibility for closing the dialog into each screen's cancel handler, and prevents er…
No security-relevant signals in the diffUI-only navigation and error-dialog suppression changesNo cryptographic, authentication, authorization, or data-handling changes
This commit is a routine merge from the project's staging branch into a feature branch. The visible code changes fix small UI/UX bugs in Stack Wallet's send screens: clearing an internal address-validation cache when the form is reset, mak…
Clearing stale address-provider state on form reset reduces the risk of stale validation data influencing a subsequent transactionFee-form caching prevents repeated network calls and accidental fee UI flicker/state races on rebuildQR scan buttons are UX additions with no visible parser/validation logic changes
This commit fixes a desktop wallet bug where the send-fee form would repeatedly re-fetch fee estimates on every screen rebuild, wasting resources and possibly flickering. It now caches the fee estimate and only retries if the previous fetc…
No security-relevant signals present in diff or commit metadataChange is a UI/UX performance and reliability improvement
This commit merges a feature branch into another work-in-progress branch. It adds QR-code scanning buttons to two desktop token send screens and resets an internal address-validation state variable when the send form is cleared. There is n…
State reset added to clearForm() to avoid stale validation dataNew QR scan entry points in token send flows (UI feature, not a vulnerability signal)
This change fixes a UI state bug in the cryptocurrency wallet's send form. When a user clears the send form, the app now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing…
UI state desynchronization between form field and validity indicatorPotential user confusion from stale valid-address stateNo input validation, cryptographic, or network-layer changes
This commit adds a QR code scanner button to two desktop cryptocurrency send forms. It is a straightforward user-interface feature addition with no apparent security relevance.
This commit adds a missing QR code scan button to two desktop token send screens in the Stack Wallet app. It is a straightforward user-interface fix that restores a feature already present on mobile and other send views; there is no indica…
This commit is purely a code-formatting cleanup. It changes line breaks and indentation in four user-interface files so the code is easier to read, but it does not change what the app actually does. There is no security relevance.
This commit fixes a UI bug in the desktop version of Stack Wallet where the send amount could be lost while the app was trying to estimate transaction fees. The fix keeps the amount 'alive' in memory so fee estimation does not accidentally…
State lifecycle issue in UI provider could lead to loss of user inputFix prevents fee estimation from silently resetting send amount to zeroNo cryptographic, authentication, or network security changes present
This commit updates the Stack Wallet app so that when a single payment is broken into multiple cryptocurrency transactions, the user sees a clear warning on the confirmation screen. It also changes the app's internal record-keeping to hand…
UI now warns users when a payment will be split into multiple on-chain transactionsInternal transaction model changed from single txid to list of txidsMultiple confirmation flows updated to iterate over all txids for notes and trade lookups
This commit fixes a performance bug in the desktop version of Stack Wallet where the app repeatedly re-fetched Bitcoin-style fee rates every time the on-screen fee form rebuilt. The change caches the fee result and only fetches again if th…
Unnecessary repeated network requests reducedFuture result cached to avoid re-execution on widget rebuildError path clears cache to allow retry
This commit fixes a UI state bug in Stack Wallet's send form. When a user clears the send form, the wallet now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old ad…
Stale UI state after form resetAddress validity not synchronized with address field resetPotential UI confusion leading to incorrect send confirmation
This is a large feature/fix merge that restores and rewrites the Xelis (XEL) cryptocurrency integration in Stack Wallet. It swaps the old hand-rolled Xelis code for a new generated native interface (XWF), adds wallet restore/backup support…
Send-flow lifecycle hardening: prepared Xelis transactions are now discarded via cancelSend when the user cancels or the widget is disposedSession-generation checks prevent stale wallet handles from being used after close/reopenMutex serialization added around send preparation, balance, history, and rescan operations
This commit is a large merge that mainly adds integration tests for a desktop 'forgot password' reset feature and makes supporting code changes to safely shut down background database workers during that reset. It also removes a large set …
New integration tests exercise a destructive 'forgot password' data-wipe featureTests assert that password store and wallet key store are deleted on successful resetTests assert that wallet files are deleted while backup and tor state are preserved
This commit lets users type multi-line notes when editing transaction and trade notes, and fixes the desktop layout so long notes scroll instead of breaking the screen. It also swaps the old `mounted` check for the newer `context.mounted` …
This commit is a large merge that mainly removes old integration tests and adds new desktop 'forgot password' reset tests. It also adds a safe-shutdown path for background Firo cache workers and databases. The changes look like defensive h…
Added safe shutdown of Firo cache isolates/SQLite databases before reset exitNew integration tests verify desktop forgot-password reset deletes secrets and preserves backupsTest harness intercepts exit() and IOOverrides to observe reset side effects
This commit fixes the desktop "forgot password" reset flow in Stack Wallet. It adds integration tests that verify the app can securely wipe its own data when a user forgets the desktop password, and it updates the Firo cache worker to clos…
Desktop password reset now closes Firo cache workers and SQLite databases before deleting app data, reducing the risk of data leakage or corruption during wipeNew integration tests assert that a successful reset removes password store (hive/desktopdata.hive), wallet key store (isar/desktopStore.isar), and wallet files while preserving backups and tor stateFailed reset scenario leaves a .reset-pending marker and removes password/key stores first, preventing the reset from being undone after partial deletion
This commit is a large merge that mainly adds a new 'prove you own a Spark address' feature to the Stack Wallet app, plus some related fixes. It also updates a dependency that handles SOCKS5 proxy connections and changes how the app decide…
New cryptographic signing path added: SparkInterface.signMessage now delegates to Spark ownership proof creation using the wallet's private key and spark derivation path.Ownership proof code rejects view-only wallets and blank messages, and searches a 100-address lookahead for the requested address before signing.Dependency upgrade: socks5_proxy 1.0.3+dev.3 -> 2.1.1, which may change SOCKS5/Tor proxy behavior; a new test verifies hostname/onion routing through a fake SOCKS server.
This commit adds a new feature to Stack Wallet that lets users prove they own a Spark (privacy) address by generating a cryptographic ownership proof. It also improves the sign/verify screens so view-only wallets can still verify proofs, a…
New cryptographic proof generation using private key material (privateKeyHex, spendKeyIndex, diversifier) inside an isolateView-only wallet guard added for proof creation (throws if isViewOnly)Message whitespace now preserved for pasted/typed challenge messages, preventing proof/verification mismatches caused by silent trimming
This commit merges several changes into a development branch. The most notable security-relevant change is a fix for how the Trocador exchange service routes traffic: it now automatically uses Tor (an anonymity network) when the user has T…
Trocador exchange API previously forced clearnet (`isOnion: false`) at every call site, bypassing Tor even when enabledNew `_useTor` getter centralizes Tor routing decision based on app feature flag and user preferenceOnion service address rotated to a new v3 .onion hostname
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityStream subprocess output in mwebd Windows build scriptby Dan Miller · 80107e9c · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Stream subprocess output in mwebd Windows build script
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityRemove build_runner step from build jobby Dan Miller · cb8face8 · May 5, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Dan Miller
Remove build_runner step from build job
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityFor Windows the use native go build when CI=true (GitHub Actions sets this automatically), and falls back to the existing WSL cross-compile path for local Windows devs. Non-Windows hosts are unchanged.by Dan Miller · 50f22c79 · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
For Windows the use native go build when CI=true (GitHub Actions sets this automatically), and falls back to the existing WSL cross-compile path for local Windows devs. Non-Windows hosts are unchanged.
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityFix hardcoded C: drive assumption in mwebd Windows build scriptby Dan Miller · e3cbdf38 · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Fix hardcoded C: drive assumption in mwebd Windows build script
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityRemove build_runner step from pipeline as mocks are committed to repoby Dan Miller · b89d1afb · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Remove build_runner step from pipeline as mocks are committed to repo
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedperf(ordinals): cache ordinal-spend check off the build pathby sneurlax · 914c31d8 · May 4, 2026 · 1 fileMessage 62 · AdequateInformational 19Details
Commit message · sneurlax
perf(ordinals): cache ordinal-spend check off the build path
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 19/100
This commit is a performance refactor, not a security fix. It moves a check that warns users if they are about to spend a Bitcoin 'ordinal' inscription UTXO from the UI build path into an asynchronous initialization step, caching the result. The warning itself and the underlying behavior are unchanged. There is no indication this patch addresses a vulnerability or that the prior code was exploitable.
Security candidatefix(shopinbit): defend against API contract driftby sneurlax · 4ca84ac1 · May 4, 2026 · 7 filesMessage 57 · ThinLow 37Details
Commit message · sneurlax
fix(shopinbit): defend against API contract drift
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 · Low 37/100
This commit is a defensive hardening patch for the ShopInBit integration in Stack Wallet. It changes how the app handles unexpected status strings and webhook event types from the ShopInBit API. Previously, unknown values were silently forced into a default known value (for example, an unrecognized ticket state was treated as a brand-new ticket). Now unknown values are explicitly marked as 'unknown,' preserved in raw form, and ignored rather than misapplied. This prevents the app from showing wrong order statuses or acting on unexpected events if the ShopInBit API changes its labels or adds new ones.
Lower-priorityfix: throw if inscription number is nullby sneurlax · 34c73f25 · May 4, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · sneurlax
fix: throw if inscription number is null
safer than colliding with the genesis inscription
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
✓ Subject identifies a change✓ 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 minor code cleanup in the Stack Wallet app's ShopInBit feature. It removes a duplicate line of code and fixes the indentation of some UI widget code. There is no security-relevant change.
Lower-priorityfix: missing early returnby julian · 8c3f6e7d · May 4, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · julian
fix: missing early return
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queueddelete unused generated fileby julian · e250f6ae · May 4, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · julian
delete unused generated file
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply deletes an unused auto-generated file that registered data adapters for a local database library called Hive. There is no functional code change, no bug fix, and no security-relevant behavior is altered.
AI review queuedremove extra spaceby julian · 0948c155 · May 4, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · julian
remove extra space
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 removes a small vertical spacing widget (an extra 8-pixel gap) from a settings screen. It is purely a cosmetic/UI layout change and has no security relevance.
Lower-priorityupdate logger for test env (and revert recursive logging thing)by julian · 2887dc16 · May 4, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · julian
update logger for test env (and revert recursive logging thing)
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritychore: update bitcoindart ref to mainby sneurlax · b78c9de6 · May 4, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · sneurlax
chore: update bitcoindart ref to main
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Informational 0/100
This commit only updates a reference (likely a Git submodule or dependency pointer) to a library called libepiccash. No actual code changes are shown, and no security-related description is provided. There is not enough information to determine whether this update fixes a security issue, adds a feature, or is routine maintenance.
AI review queuedfix(firo): fail empty Spark auto mintsby Reuben Yap · b8f66850 · May 4, 2026 · 1 fileMessage 57 · ThinLow 32Details
Commit message · Reuben Yap
fix(firo): fail empty Spark auto mints
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 · Low 32/100
This commit adds a safety check to Stack Wallet's Firo Spark auto-minting feature. Previously, if the wallet tried to automatically convert all eligible coins into Spark private coins and somehow produced no transactions, it would silently return an empty result. Now it throws a clear error instead. This prevents the wallet from incorrectly assuming a successful private mint happened when nothing was actually sent.
AI review queuedfix(firo): tighten Spark mint fee accountingby Reuben Yap · 10ced8df · May 4, 2026 · 1 fileMessage 57 · ThinLow 42Details
Commit message · Reuben Yap
fix(firo): tighten Spark mint fee accounting
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 · Low 42/100
This commit tightens how Stack Wallet calculates and checks fees when creating privacy-preserving 'Spark mint' transactions for the Firo cryptocurrency. It fixes a loop that could keep charging fees after outputs were drained, adds an error when a user tries to auto-mint all coins but the balance is too small to pay the fee, and adds a final sanity check comparing the expected fee against the actual fee built into the transaction. The changes appear aimed at preventing incorrect or excessive fees, or transactions that fail silently.
AI review queuedfix: Spark generate-next-address diversifierby levoncrypto · ccb101bd · May 2, 2026 · 1 fileMessage 57 · ThinLow 41Details
Commit message · levoncrypto
fix: Spark generate-next-address diversifier
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 · Low 41/100
This one-line change fixes how the wallet picks the next Spark privacy address. Previously it looked at the current regular receiving address to decide the next Spark address number (diversifier). Now it correctly looks at the current Spark receiving address. Using the wrong starting number could cause address reuse or generate addresses that collide with already-used ones, which weakens the privacy guarantees Spark is designed to provide.
AI review queuedreset private balance changesby levoncrypto · 70acbe6d · May 2, 2026 · 4 filesMessage 35 · OpaqueLow 41Details
Commit message · levoncrypto
reset private balance changes
35/100 · OpaqueMessage clarity
✓ 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 41/100
This commit changes how Stack Wallet caches and resets Firo Spark private-balance data. It removes a safety fallback that refetched the full anonymity set when the local cache size looked inconsistent, switches from 'insert-or-ignore' to plain inserts for Spark coins, and simplifies the 'clear Spark cache' button so it only wipes the shared cache and no longer resets per-wallet metadata. A separate change also fixes which address type is used when generating the next Spark receiving address. The overall effect is a reset/rework of private balance tracking, but the commit message and diff alone do not clearly state whether this fixes a security bug or is just a reliability refactor.
AI review queuedrebase 876feb6ceby levoncrypto · 63874c6b · May 2, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · levoncrypto
rebase 876feb6ce
18/100 · OpaqueMessage clarity
✓ 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 15/100
This commit only updates the version numbers and cryptographic hashes of several Dart/Flutter test and utility libraries in the pubspec.lock dependency lock file. There is no indication of a security fix, vulnerability patch, or code change affecting the wallet application itself.
AI review queuedsmall fixesby levoncrypto · ae73bb43 · May 2, 2026 · 7 filesMessage 0 · OpaqueLow 31Details
Commit message · levoncrypto
small fixes
0/100 · OpaqueMessage clarity
! Very short subject! 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 · Low 31/100
This commit is a collection of small fixes in the Stack Wallet app. The most notable changes correct how Firo masternode registration transactions are signed and built, fix a bug where the app might pick the same address for both collateral and owner, and improve how the app detects and navigates after a masternode transaction. There are also UI layout tweaks and a change to the Campfire app configuration so it uses the main Firo network instead of the test network. The commit message gives no indication these are security fixes, and the changes look like ordinary bug fixes rather than patches for an exploitable vulnerability.
Lower-priorityUse cygpath on Windows CI, fall back to wslpath for WSLby Dan Miller · a3c4eb96 · May 2, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Use cygpath on Windows CI, fall back to wslpath for WSL
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityInstall libopencv-dev in CI image for camera_linux buildby Dan Miller · b2bfbf55 · May 2, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Install libopencv-dev in CI image for camera_linux build
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritySpeed up CI image pull by switching to GHCR and adding a minimal test stageby Dan Miller · 5d6d09e7 · May 2, 2026 · 3 filesMessage 60 · AdequateTriage 0Details
Commit message · Dan Miller
Speed up CI image pull by switching to GHCR and adding a minimal test stage
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityUse GHCR for docker image registry and add binary lib download scripts for ios,mac,windowsby Dan Miller · c84020e9 · May 2, 2026 · 5 filesMessage 50 · ThinTriage 0Details
Commit message · Dan Miller
Use GHCR for docker image registry and add binary lib download scripts for ios,mac,windows
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body