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

1053 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.

338security candidates411second-pass queue749AI analyses
77commits · 30 days
175commits · 60 days
600commits · 180 days
1005commits · 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.

51/100 average clarity
33Strong · 80–100
316Adequate · 60–79
513Thin · 40–59
191Opaque · 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.
Navid Rahimi1017154
sneurlax339158241062
julian347112269044
Julian19741144043
Dan Miller831525053
Reuben Yap20318052
Cyrix12615211049
julian-CStack222049
levoncrypto24121043
Tritonn204412052
cassandras-lies413048
NyanCatTW1111045
Analysis record

Published AI watches

Last scanned 41 minutes ago

Informational 24 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1469 from Cyrix126/building_dialog_cancel

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
94e6da66by Julian+68−8412 files
No security note in commit
Informational 20 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into building_dialog_cancel

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
0485b166by Julian+194−56 files
No security note in commit
Informational 17 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1468 from Cyrix126/desktop_fee_form_refetch

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
62432946by Julian+176−52 files
No security note in commit
Informational 17 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into desktop_fee_form_refetch

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)
8a72c82fby Julian+18−04 files
No security note in commit
Low 32 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1467 from Cyrix126/clear_send_form_validity

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
d3383b4eby Julian+2−02 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into clear_send_form_validity

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.

22560a59by Julian+16−02 files
No security note in commit
Informational 20 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1466 from Cyrix126/desktop_token_qr_button

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…

47f6d369by Julian+16−02 files
No security note in commit
Informational 15 AI analysisMessage 18 · Opaque
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

style: format

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.

ae45aba8by Cyrix126+47−524 files
No security note in commit
Informational 23 AI analysisMessage 62 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

fix: stop estimating the desktop fee for a zero amount

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
90c91bdeby Cyrix126+22−02 files
No security note in commit
Low 32 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

show split tx warning on confirm screen

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
80343a5aby Julian+376−23916 files
No security note in commit
Informational 18 AI analysisMessage 62 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

fix: stop refetching the desktop fee rates on every rebuild

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
a1ca9292by Cyrix126+154−52 files
No security note in commit
Low 34 AI analysisMessage 62 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

fix: reset the address validity when clearing the send form

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
43dd0477by Cyrix126+2−02 files
No security note in commit
Low 35 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1450 from Ez3kiel-dev/fix/xelis-integration

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
ad945d43by Julian+4298−162634 files
No security note in commit
Low 32 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into fix/xelis-integration

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
b0e5d35aby Julian+2678−330378 files
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1361 from cypherstack/fix/305-multiline-transaction-notes

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` …

5172e63eby Julian+402−1113 files
No security note in commit
Low 32 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into fix/305-multiline-transaction-notes

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
21491edbby Julian+2352−319075 files
No security note in commit
Moderate 57 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1455 from cypherstack/fix/desktop-pw-reset

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
055e6c6bby Julian+1077−297154 files
No security note in commit
Low 37 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into fix/desktop-pw-reset

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.
d9b5cc02by Julian+1275−21923 files
No security note in commit
Low 34 AI analysisMessage 83 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1439 from navidR/dev/navidr/spark-name-verification

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
a5411a50by Julian+1097−16616 files
No security note in commit
Low 39 AI analysisMessage 60 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into dev/navidr/spark-name-verification

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
92955848by Julian+122−507 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.

Lower-priorityfeat(ui): expose configurable MWC API secret in add/edit node formby sneurlax · 47bac5f3 · May 13, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · sneurlax

feat(ui): expose configurable MWC API secret in add/edit node form

chore: dart format fix/mwc

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfeat(ui): persist nodeApiSecret to NodeModel on node saveby sneurlax · 72530c8e · May 13, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · sneurlax

feat(ui): persist nodeApiSecret to NodeModel on node save

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedchore: dart formatby sneurlax · 5f9ca3a4 · May 13, 2026 · 6 filesMessage 40 · ThinInformational 15Details
Commit message · sneurlax

chore: dart format

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 15/100

This commit is purely a code-style cleanup: it runs the Dart formatter on six files related to PayNym features. No logic, behavior, or security-sensitive code was changed. It is not a security fix and does not introduce any obvious vulnerability.

Lower-priorityuse drift/sqlite to store order ids instead of piggybacking in the preferences storeby julian · e37737e8 · May 13, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · julian

use drift/sqlite to store order ids instead of piggybacking in the preferences store

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityfeat(db): create a shared drift database with initial table for cake pay order IDsby julian · 2c790e2a · May 13, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · julian

feat(db): create a shared drift database with initial table for cake pay order IDs

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
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.

AI review queuedrefactor: exolix apiby julian · db0c225e · May 13, 2026 · 13 filesMessage 40 · ThinInformational 12Details
Commit message · julian

refactor: exolix api

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 12/100

This commit is a code reorganization: the Exolix exchange API code is split from one large file into several smaller files (DTOs, helpers, and the API client). The actual logic, behavior, and security checks remain the same. There is no indication this fixes a security bug or introduces a new vulnerability.

Lower-priorityfix(build): update prebuild scriptby julian · f9c400c5 · May 13, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · julian

fix(build): update prebuild script

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore: update ref back to cypherstack#mainby sneurlax · eebee9ba · May 13, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · sneurlax

chore: update ref back to cypherstack#main

as of bdc0c0788d1d6dfb04863a793955f848ba1624a8

see 783dbdeded3859cd0e93b0ad4d90732e96b77713

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI review queuedfeat(Exolix): initial integrationby julian · e496150e · May 12, 2026 · 16 filesMessage 47 · ThinLow 30Details
Commit message · julian

feat(Exolix): initial integration

47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 30/100

This commit adds Exolix as a new cryptocurrency exchange provider inside Stack Wallet. It introduces roughly 1,500 lines of code for API communication, trade creation, rate quotes, currency caching, and UI icons/status handling. There is no claim in the commit or supplied references that this fixes a security bug; it is a feature integration. The code does touch sensitive areas (network requests, API keys, transaction status parsing, decimal handling for money), but the diff itself does not show an obvious vulnerability. A few spots deserve closer review: the API key fallback uses a hard-coded placeholder check, the new exchange is marked as possibly supporting Tor, and transaction status strings are parsed with broad fallbacks. These are normal integration risks rather than confirmed flaws.

Lower-priorityfix: json printer bugby julian · 277a1374 · May 12, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · julian

fix: json printer bug

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedchore: autoformatby julian · 6d9752f4 · May 12, 2026 · 1 fileMessage 30 · OpaqueInformational 15Details
Commit message · julian

chore: autoformat

30/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! 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 is purely a code formatting cleanup in a single theme file. It adds spaces to comment markers and rewraps long function calls onto single lines. There are no functional changes, no security fixes, and no behavior differences.

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.

Lower-prioritysupport private (Spark) balance for masternode collateralby Narek · 4438aab9 · May 11, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Narek

support private (Spark) balance for masternode collateral

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityDon't build windows FFI libmwebd.dllby Dan Miller · 71f3628a · May 11, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Dan Miller

Don't build windows FFI libmwebd.dll

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityUpdate openjdk in CI imageby Dan Miller · 0a1eaf1c · May 11, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Dan Miller

Update openjdk in CI image

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedupdate Masternode UI for Firoby levoncrypto · 8cedfecf · May 9, 2026 · 8 filesMessage 45 · ThinInformational 23Details
Commit message · levoncrypto

update Masternode UI for Firo

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 23/100

This commit updates the Firo masternode user interface in Stack Wallet. It changes how the app guides users to create a 1000 FIRO collateral transaction, switches some dialog navigation to use the root navigator, and removes the automatic masternode registration flow that previously followed a successful collateral send. There is no clear security vulnerability introduced, but the changes touch navigation and state handling in ways that could affect stability or user experience.

Lower-priorityfix: correct linux CMakeLists paths for epiccash/mwc .so installsby Dan Miller · 7f3c3fa4 · May 9, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Dan Miller

fix: correct linux CMakeLists paths for epiccash/mwc .so installs

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
documentation-only discount
AI review queuedformat Spark interfaceby Reuben Yap · 83d28889 · May 8, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Reuben Yap

format Spark interface

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 · Informational 15/100

This commit only reformats code in a single Dart file. It splits one exception message across multiple lines and collapses a multi-line fee calculation into a single line. There are no functional changes, no bug fixes, and no security-related modifications.

Lower-priorityrefactor(cakepay ui): clean up vendors view codeby julian · 61ca1730 · May 7, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · julian

refactor(cakepay ui): clean up vendors view code

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfeat: keep GTK_CSD env var as opt-in for GNOME header barby sneurlax · dd156702 · May 7, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · sneurlax

feat: keep GTK_CSD env var as opt-in for GNOME header bar

preserves the user-facing escape hatch added in #1211 by flipping it from opt-out to opt-in: the traditional title bar is now the default, and GTK_CSD=1 brings back the GNOME-style header bar without rebuilding.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityfix: restore template placeholder and GApplication property nameby sneurlax · c715d97a · May 7, 2026 · 1 fileMessage 42 · ThinTriage 0Details
Commit message · sneurlax

fix: restore template placeholder and GApplication property name

42/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language
Lower-prioritylinux: don't use GNOME's custom title barby pierrelasse · 759d8448 · May 7, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · pierrelasse

linux: don't use GNOME's custom title bar

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityfix(desktop ui): remove expanded parent of iconby julian · b81e924a · May 7, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · julian

fix(desktop ui): remove expanded parent of icon

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(firo): masternodes_home_view.dart db query runtime errorby julian · 24cc0838 · May 6, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · julian

fix(firo): masternodes_home_view.dart db query runtime error

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body