SW
← All projectsStack Wallet

Stack Wallet

Actively maintained multi-coin self-custody wallet with Monero support and on-device keys.

MoneroPrivacy protocolsSoftware walletsNormal
Repository coverage

1166 commits in the local evidence base

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.

376security candidates450second-pass queue826AI analyses
104commits · 30 days
161commits · 60 days
472commits · 180 days
945commits · 365 days
Backfill bands
Sep 27 → Mar 31404 seen73 candidatesComplete
Mar 31 → Jul 29463 seen238 candidatesComplete
Jul 29 → Aug 2887 seen8 candidatesComplete
Aug 28 → Sep 2753 seen6 candidatesComplete
Commit communication

Does the history explain itself?

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
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Julian24159176246
sneurlax380170270163
kroplabeskidu333176
slopbot9k1628163
Navid Rahimi1017154
julian347112269044
Dan Miller841525053
Cyrix12618414049
Reuben Yap20318052
julian-CStack222049
levoncrypto24121043
cassandras-lies413048
Analysis record

Published AI watches

Last scanned 38 minutes ago

Moderate 57 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1528 from cypherstack/fix/taproot-input-sequence

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
05b0ad33by Julian+1−11 file
No security note in commit
Low 35 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1541 from cypherstack/rotate-receiving-address-types

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
01be23d6by Julian+1288−210 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1537 from cypherstack/fix/simplex-current-receiving-address

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
f41c799eby sneurlax+239−593 files
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Test the Buy form's Choose from Stack flow in the real app

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…

ba44e64cby slopbot9k+1022−27 files
No security note in commit
Moderate 52 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Rotate used receiving addresses on every derivation path

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…

Address reuse mitigationPrivacy improvementWallet receive-address rotation
8998a949by slopbot9k+243−02 files
Vendor flagged security relevance
Low 36 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1529 from cypherstack/fix/electrs-vanished-tx

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
1d319093by Julian+4−31 file
No security note in commit
Informational 12 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1505 from cypherstack/repro-dnix-packages

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
9c89083fby Julian+4431−69337 files
No security note in commit
Moderate 61 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into repro-dnix-packages

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
e517d08eby Julian+7700−164556 files
No security note in commit
Moderate 61 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1510 from cypherstack/electrum-client-per-wallet-refactor

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
a7d86094by Julian+7700−164556 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Stop describing a certificate approval as a pin

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…

4b88ce9aby slopbot9k+3−32 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Format the view-only restore view

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.

6d56c42bby slopbot9k+8−91 file
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge remote-tracking branch 'upstream/staging' into electrumx-per-wallet

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
16b06913by slopbot9k+3251−249339 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1511 from Cyrix126/share_send_fee_logic

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
40c9a054by Julian+3176−249237 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1509 from cypherstack/feat/monero-signing

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 …

7659bc86by Julian+75−13 files
No security note in commit
Informational 17 AI analysisMessage 90 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

feat(xmr): sign and verify messages

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
6c49e3ceby sneurlax+75−13 files
No security note in commit
Low 43 AI analysisMessage 86 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Drop vanished unconfirmed txs on electrs too

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
a31b28b6by sneurlax+4−31 file
No security note in commit
Informational 17 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1506 from cypherstack/fix/sol-add-token-new-wallet

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
ed3f1cd0by Julian+241−1014 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1483 from cypherstack/fix/eth-add-token-new-wallet

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)
213c6b0cby Julian+171−552 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Format Solana wallet picker changes for the current Dart SDK

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…

e93f0521by sneurlax+78−1012 files
No security note in commit
Informational 18 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Fix Ethereum picker empty state during wallet registration

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…

a729e6d5by sneurlax+139−122 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatefix(ui): chat bubble colorsby julian · f1b14f11 · May 20, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · julian

fix(ui): chat bubble colors

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit only changes the colors used for chat message bubbles in a customer-support ticket screen. It swaps hard-coded or theme-mismatched colors for theme-consistent primary/secondary button colors so the chat looks correct in light and dark modes. There is no security relevance.

Security candidaterefactor(ui): keep functionality the same as much as possible but refactor widget tree clean up and styling fixesby julian · 0f0d582f · May 20, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · julian

refactor(ui): keep functionality the same as much as possible but refactor widget tree clean up and styling fixes

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit is a user-interface cleanup for the ShopInBit ticket and request screens. It swaps some dialog and container widgets, extracts repeated list-row code into helper widgets, and changes how a loading spinner is shown during ticket sync. There is no indication of a security fix or vulnerability being addressed.

Security candidaterefactor(db): use drift/sqlite instead of isarby julian · f357b4a7 · May 20, 2026 · 28 filesMessage 57 · ThinInformational 11Details
Commit message · julian

refactor(db): use drift/sqlite instead of isar

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 11/100

This commit is a routine internal refactor that moves the app's shared database code from one location to another and switches some ShopInBit ticket data from the Isar database to a Drift/SQLite database. It is not described as a security fix, and the visible changes do not introduce obvious ways for an attacker to steal funds or data. The main risk is that any database migration could accidentally lose or corrupt user data, but nothing in the supplied diff proves that happened.

Security candidatefix(ui): check correct contextby julian · fd53f9fe · May 19, 2026 · 1 fileMessage 57 · ThinInformational 16Details
Commit message · julian

fix(ui): check correct context

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 16/100

A one-line UI fix changes a safety check from 'if the widget is still in the tree' to 'if the Flutter BuildContext is still valid' before showing a temporary info banner. This is a routine Flutter correctness fix that prevents a possible crash when a screen is closed while the banner is being prepared. There is no direct evidence in the commit that this is a security issue.

Security candidatefix(ui): button spacingby julian · 9dad75d7 · May 19, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · julian

fix(ui): button spacing

40/100 · ThinMessage clarity
✓ 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 only adjusts the spacing between buttons on a settings screen, making gaps slightly wider on desktop and in a couple of places on mobile. It is a visual user-interface tweak with no security relevance.

Security candidatefix(ui): clean up flow logic and state issuesby julian · 1c6ffa9a · May 19, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · julian

fix(ui): clean up flow logic and state issues

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit is a routine UI cleanup in the Stack Wallet app's ShopInBit settings screen. It removes an extra 'verify your key' dialog that was managed inside the same screen and turns it into a separate, self-contained dialog widget. The visible behavior—asking the user to re-enter their saved customer key before continuing—appears unchanged. There is no clear security fix or vulnerability here; it looks like a code-quality refactor.

Security candidatechore: add some toString()sby julian · 8ed3d339 · May 19, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · julian

chore: add some toString()s

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit adds human-readable toString() methods and helper toMap() methods to three data classes that describe shopping tickets. It only changes how objects look when printed or logged; it does not alter how data is stored, transmitted, validated, or protected. There is no security issue visible in the change.

Security candidaterefactor(shopinbit): Store shop in bit settings using Drift, use providers for drift shared db and shopinbit service, and some general clean up and tweaksby julian · fa5fa812 · May 19, 2026 · 29 filesMessage 62 · AdequateInformational 19Details
Commit message · julian

refactor(shopinbit): Store shop in bit settings using Drift, use providers for drift shared db and shopinbit service, and some general clean up and tweaks

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 19/100

This commit is a routine refactor of the ShopinBit feature in Stack Wallet. It moves settings like whether the user accepted guidelines, completed setup, and their display name from the previous storage mechanism into a Drift/SQLite database, and switches UI code to use Riverpod providers for that database and the ShopInBit service. The diff shows no obvious malicious intent, no new network calls, no weakening of encryption, and no exposed secrets. It is primarily a code-quality and architecture change.

Security candidateFix Android APK signing (keystore format) in CI build jobby Dan Miller · ec2cabc3 · May 19, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · Dan Miller

Fix Android APK signing (keystore format) in CI build job

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 18/100

This commit fixes a small but real bug in the automated build pipeline for Android. Previously, the build script used `echo` to write the signing keystore from a base64-encoded secret. If the secret was empty or missing, `echo` would still create an empty file and the build would continue, potentially producing an unsigned or broken APK. The fix uses `printf '%s'` to avoid adding a trailing newline, and adds a check that aborts the build if the keystore secret is empty. This is a reliability and correctness improvement rather than a direct security vulnerability in the app itself.

Security candidateFix Android APK signing (keystore format) in CI build jobby Dan Miller · e3256156 · May 19, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · Dan Miller

Fix Android APK signing (keystore format) in CI build job

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Informational 18/100

This commit changes the GitHub Actions build workflow for the Stack Wallet Android app. It adds a step that converts the uploaded Android signing keystore from its original format into the PKCS12 format before building the APK. This is a CI/build pipeline fix and does not, on its own, introduce a vulnerability. It does mean the CI job now handles the app's private signing keystore and its password, so the security of the build pipeline remains important.

Security candidatefix: allow shopinbit car request status updatesby julian · 7ddaa909 · May 19, 2026 · 1 fileMessage 57 · ThinInformational 17Details
Commit message · julian

fix: allow shopinbit car request status updates

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 17/100

This commit removes a special workaround that previously skipped status and message updates for car-research tickets in a shopping feature. Now those tickets will call the same backend endpoints as other tickets. The change appears to be a functional bug fix rather than a security fix, but it slightly increases the amount of data exchanged with the backend for car-research tickets.

Security candidatefix: throw instead of silent failure leading to invalid enum value returns. And some other cleanupby julian · c6b313bb · May 19, 2026 · 5 filesMessage 62 · AdequateInformational 24Details
Commit message · julian

fix: throw instead of silent failure leading to invalid enum value returns. And some other cleanup

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 24/100

This commit changes how the Stack Wallet app handles unexpected status values from its ShopInBit partner service. Previously, if the server sent an unknown status string, the app silently replaced it with a default value (e.g., treating an unknown ticket state as a brand-new ticket). Now the app throws an exception instead. The commit also moves some UI label/color code into the enum definitions and removes duplicate code. The change is a defensive fix that prevents the app from misrepresenting order or webhook states, but it could also cause crashes if the server ever introduces new status values that older app versions don't recognize.

Security candidatefix: This does not actually return a 403 when testing and is required to get a status update. Commenting out for now as otherwise the request will stay pending for ever in the UIby julian · a4d82ec1 · May 19, 2026 · 1 fileMessage 84 · StrongInformational 11Details
Commit message · julian

fix: This does not actually return a 403 when testing and is required to get a status update. Commenting out for now as otherwise the request will stay pending for ever in the UI

84/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 11/100

A developer commented out a special-case skip that prevented 'car research' support tickets from having their status checked. The change makes the app try to fetch status for those tickets too, fixing a UI hang where the request appeared to stay pending forever. There is no clear security problem in the diff itself; it is a functional bug fix.

Security candidaterefactor: testing AI refactoringby julian · e9beb4ab · May 19, 2026 · 14 filesMessage 57 · ThinInformational 10Details
Commit message · julian

refactor: testing AI refactoring

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 10/100

This commit is a large code cleanup that splits one big ShopinBit order form file into smaller, easier-to-maintain pieces. It does not appear to change what the app does or how user data is handled; it mostly moves existing UI code around. There is no clear security problem visible in the diff, but because the change is so large and was labeled as 'testing AI refactoring,' it could accidentally introduce subtle bugs that would need normal testing to catch.

Security candidatefix(ui): desktop shopinbit dialog flow nested navigationby julian · eba53250 · May 18, 2026 · 11 filesMessage 62 · AdequateInformational 17Details
Commit message · julian

fix(ui): desktop shopinbit dialog flow nested navigation

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 17/100

This commit is a user-interface refactor for the desktop ShopinBit (crypto concierge shopping) flow. It replaces a brittle pattern of opening and closing separate dialogs for each step with a single dialog that contains its own nested navigator. There is no clear security bug being fixed; the changes are about navigation consistency and code maintainability. The only security-relevant observation is that the new route generator validates that navigation arguments are the expected order model, which slightly hardens type handling, but this is a normal defensive coding practice rather than a fix for a known vulnerability.

Security candidateCI workaround for github actions runnerby Dan Miller · bad423c8 · May 16, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Dan Miller

CI workaround for github actions runner

45/100 · ThinMessage clarity
✓ 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 is a routine GitHub Actions CI maintenance change. It adds the 'staging' branch to automated build triggers and fixes a Windows build problem where the CI runner could not create symbolic links (shortcuts) for app assets, so the workflow now copies those asset folders instead. There is no indication this affects user security or wallet safety.

Security candidatechore: fix and clean up WIPby julian · 5eaf945e · May 15, 2026 · 6 filesMessage 37 · OpaqueInformational 14Details
Commit message · julian

chore: fix and clean up WIP

37/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 14/100

This commit is a routine UI cleanup for work-in-progress gift-card and shopping features. It swaps custom text fields and dialogs for shared reusable widgets, removes unused focus nodes, and fixes small layout and error-message details. There is no clear security problem in the changes, and nothing in the commit message or diff indicates a security fix.

Security candidatefix: context.mounted check (and a bunch of auto format)by julian · 211971b5 · May 14, 2026 · 1 fileMessage 62 · AdequateInformational 16Details
Commit message · julian

fix: context.mounted check (and a bunch of auto format)

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 path
AI analysis · Informational 16/100

This commit fixes a Flutter widget state check in a cryptocurrency selection screen. It changes `mounted` to `context.mounted` before navigating back. The rest of the change is automatic code formatting. The fix prevents a potential app crash when a user presses the back button after the screen has already been disposed.

Security candidatechore(mwc): bump flutter_libmwcby sneurlax · 962755f2 · May 14, 2026 · 1 fileMessage 47 · ThinInformational 4Details
Commit message · sneurlax

chore(mwc): bump flutter_libmwc

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 4/100

This commit only updates a dependency reference (flutter_libmwc) for the MWC cryptocurrency plugin. No code changes are shown, and there is no information about what changed in the dependency itself. Based on the available materials, this looks like a routine maintenance update rather than a security fix.

Security candidatefix(mwc): bump flutter_libmwc for get_chain_height chain type fixby sneurlax · c5229444 · May 13, 2026 · 1 fileMessage 77 · AdequateInformational 21Details
Commit message · sneurlax

fix(mwc): bump flutter_libmwc for get_chain_height chain type fix


diag(mwc): panic hook, listener fallback, and scanOutputs catch_unwind

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 21/100

This commit updates a cryptocurrency plugin dependency (flutter_libmwc) used by Stack Wallet for MWC coin support. The title says it fixes how the wallet asks the MWC library for the current chain height, and the message mentions adding panic handling and fallback logic in that plugin. The actual code change is only one line in a submodule reference, so we cannot see what really changed inside the plugin. There is no clear security claim by the project, and no independent report is cited.

Security candidatechore(ui): WIP clean upby julian · 7615bd77 · May 13, 2026 · 9 filesMessage 30 · OpaqueInformational 16Details
Commit message · julian

chore(ui): WIP clean up

30/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 16/100

This commit is a routine UI cleanup. It removes a hidden developer-only feature that let testers manually override CakePay order statuses on their own device, and replaces several copy-pasted loading spinner widgets with a single shared loading widget. There is no indication this was a security fix or that the removed feature could be exploited by normal users.

Security candidateios: use prebuilt frostdart lib (drops frostdart Rust version pin)by Dan Miller · b3670584 · May 12, 2026 · 3 filesMessage 50 · ThinInformational 14Details
Commit message · Dan Miller

ios: use prebuilt frostdart lib (drops frostdart Rust version pin)

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 14/100

This iOS build change switches the FROST cryptographic library from being compiled from source during app building to being downloaded as a prebuilt binary. It also removes a pinned Rust compiler version. The change itself is a build-system convenience, but it slightly increases supply-chain risk because the app now relies on a prebuilt library whose contents are not rebuilt from public source at build time, and the Rust compiler version is no longer fixed.

Security candidatechore(source structure/naming): organize and name accordinglyby julian · 931d2058 · May 6, 2026 · 5 filesMessage 62 · AdequateInformational 15Details
Commit message · julian

chore(source structure/naming): organize and name accordingly

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit simply moves three Dart files from one folder to another and updates the corresponding import paths. It is a routine code organization change with no visible security implications.

Security candidateui(desktop shopinbit): clean up look and feelby julian · 43bb7e31 · May 6, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · julian

ui(desktop shopinbit): clean up look and feel

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit is a purely cosmetic user-interface update for the desktop ShopInBit setup screen. It swaps some visual widgets, removes an unused focus highlight, adjusts padding and layout, and makes the dialog height adapt to the window size. There is no security-relevant change.

Security candidateBump flutter_libmwc to v0.1.2 (iOS shasum fix)by Dan Miller · d0ecc2dc · May 5, 2026 · 1 fileMessage 45 · ThinInformational 10Details
Commit message · Dan Miller

Bump flutter_libmwc to v0.1.2 (iOS shasum fix)

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 10/100

This commit updates a single cryptocurrency plugin dependency (flutter_libmwc) to version 0.1.2, with the stated reason being an iOS checksum ('shasum') fix. The actual code changes are not visible because the diff was not provided. A checksum fix normally means a downloaded file's hash was corrected so the build can verify it was not corrupted or tampered with during download. It is a build-integrity issue, not a live vulnerability in the wallet itself, unless the wrong checksum was hiding a malicious replacement. There is no evidence in the supplied materials of malicious intent or a security breach.