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…
Merge pull request #1480 from cypherstack/verify-inputs
verify legacy inputs
68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · High 75/100
This commit adds cryptographic verification to stop a malicious or compromised ElectrumX server from lying to the wallet. Before this change, the wallet trusted the server for transaction sizes, UTXO values, and unconfirmed transaction details. A dishonest server could trick the user into overpaying fees, accepting fake payments, or trying to spend coins that do not exist. The patch makes the wallet fetch raw transaction bytes, check that they hash to the claimed transaction ID, verify that the wallet itself signed the inputs, and, for older P2PKH coins, confirm the spent amounts against the parent transaction. If verification fails, the wallet drops or blocks the suspicious transaction or coin.
✓ Subject identifies a change✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · High 80/100
This commit adds cryptographic checks that make sure transaction data coming from ElectrumX servers really was signed by the user's wallet and matches the amounts the wallet expects. Before this change, a malicious or buggy server could lie about a coin's value, a pending transaction's size, or even invent a fake spend that the wallet would trust. The fix verifies raw transaction bytes, checks signatures, and for older 'legacy' P2PKH inputs it also fetches and checks the parent transaction to confirm the amount. If verification fails, the wallet now blocks the coin or drops the unverified transaction instead of using it.
Lower-prioritychore(deps): take cs_openalias 0.0.1 from pub.devby sneurlax · f0409459 · Oct 29, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · sneurlax
chore(deps): take cs_openalias 0.0.1 from pub.dev
cs_openalias and its constituent packages (openalias, dnssec_resolver, doh_transport) are published, so depend on the hosted release and drop the git overrides that stood in for them.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Merge remote-tracking branch 'github-cs-check/feat/openalias' into feat/openalias
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 27/100
This commit is mostly routine maintenance: updating Rust compiler versions, refreshing third-party library references, switching block-explorer URLs, and adding a Linux packaging helper that removes an executable-stack flag from bundled wallet libraries. The most security-relevant change is the new helper script, which prevents modern Linux from rejecting (or potentially mishandling) certain native libraries. There is no clear vulnerability being fixed, no vendor security disclosure, and no independent researcher credited.
Security candidateMerge branch 'staging' into feat/openaliasby Julian · f9e48dd5 · Oct 29, 2026 · 14 filesMessage 45 · ThinInformational 23Details
Commit message · Julian
Merge branch 'staging' into feat/openalias
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 23/100
This merge commit mostly updates build tooling, Rust compiler versions, Flutter plugin wiring, and block-explorer URLs. The most security-relevant change is a new Linux release script that removes the executable-stack flag from bundled wallet libraries and refuses to ship any other library that still requests one. This is a hardening/fix for a deployment issue where modern Linux systems could reject or warn about those libraries. There are no obvious malicious code changes or direct exploit patches visible in the diff.
AI review queuedMigrate the Fact0rn default node to allow Torby sneurlax · 82b494ad · Oct 28, 2026 · 3 filesMessage 78 · AdequateLow 25Details
Commit message · sneurlax
Migrate the Fact0rn default node to allow Tor
updateDefaults keeps the saved node's tor and clearnet flags, so existing installs kept the old clearnet-only Fact0rn default even though it now allows Tor. With Tor turned on that node is rejected and Fact0rn cannot refresh or pass the node test.
Add a one-time migration that enables Tor on the saved Fact0rn default node. Only a node that still matches the old shipped default on every field the user can edit (host, port, name, SSL, failover, login, clearnet only) is touched, so a node the user customised keeps its settings. Clearnet stays enabled, so nothing changes with Tor off, and later choices are left alone.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Low 25/100
This commit fixes a bug where the Fact0rn cryptocurrency default node in Stack Wallet stayed set to 'clearnet only' even after the app shipped a new default that supports Tor. For users who turned on Tor, the wallet could no longer connect to that node, so Fact0rn balances would not refresh and the node health test would fail. The patch adds a one-time database migration that flips Tor support on for the default Fact0rn node, but only if the user has not customized it. It is a connectivity/usability fix, not a vulnerability that lets an attacker steal funds or run code.
Scope cached ShopinBit attachments by customer key
TorAwareNetworkImage keys its cache on the url alone, so an attachment path fetched under one customer key would be served from cache to a later customer key without an authenticated request. Add an optional cacheScope that is part of the key, and pass the ShopinBit customer key there. The bearer token stays out of the key so a refreshed token does not refetch.
The key is captured together with the request response rather than read from the widget when building the image: FutureBuilder keeps showing the previous snapshot while a new future is pending, and that snapshot must not be paired with a later customer's scope.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Moderate 60/100
This commit fixes a privacy bug in Stack Wallet's image caching. When the app showed customer support attachments from ShopinBit, it cached images using only the web address. Because the same attachment path can return different files for different customers, a later customer could briefly see another customer's cached image without a fresh permission check. The patch adds a 'customer key' to the cache key so each customer's images stay separate, and it makes sure the key is tied to the actual downloaded response rather than the on-screen widget state.
Lower-priorityfix(openalias): count a resolved alias's lifetime from the lookup startby sneurlax · d5ad2c98 · Oct 28, 2026 · 3 filesMessage 95 · StrongTriage 0Details
Commit message · sneurlax
fix(openalias): count a resolved alias's lifetime from the lookup start
The recipient's TTL is what remained when the answer arrived, so taking the clock after a slow lookup let a cached address outlive it by up to the lookup time. Add recipient after an expired preview now has a test too: it keeps the typed alias and never pays the stale address.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedfix(openalias): expire a resolved alias with its TTLby sneurlax · b1366075 · Oct 28, 2026 · 5 filesMessage 85 · StrongModerate 60Details
Commit message · sneurlax
fix(openalias): expire a resolved alias with its TTL
A repeated Preview or Add recipient reused the cached address for as long as the form lived, so a later send could pay an address the recipient had since replaced. Reuse now ends with the answer's TTL, capped at an hour.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This commit fixes a bug in Stack Wallet where an OpenAlias recipient address (for example, an email-like alias that resolves to a crypto address) could be reused indefinitely once it was first looked up. If the recipient later changed their address, the wallet might still send funds to the old, cached address. The fix makes the cached address expire after the time-to-live (TTL) returned by the OpenAlias lookup, capped at one hour, so the wallet will re-resolve the alias before sending if the cached answer is stale.
AI review queuedfix(openalias): drop the resolved alias when the recipient field changesby sneurlax · eb9d88da · Oct 28, 2026 · 3 filesMessage 85 · StrongLow 36Details
Commit message · sneurlax
fix(openalias): drop the resolved alias when the recipient field changes
Clearing the field and typing the same alias again reused the old lookup. Every change of the address now drops a lookup for another alias, so the cleared field ends it.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 36/100
This commit fixes a bug in Stack Wallet's OpenAlias lookup for cryptocurrency sending. Previously, if a user cleared the recipient field and retyped the same alias, the wallet reused the old address lookup instead of fetching it again. The fix now drops the cached lookup whenever the recipient text changes, ensuring a fresh lookup occurs. This is a correctness and potential security fix because a stale or attacker-controlled alias resolution could be reused when the user expected a new lookup.
The recipient now carries a required ttl, so the test fakes pass one.
Resolved with `flutter pub get` against the ~/.pub-cache git mirror of github.com/cypherstack/cs_openalias fetched from the local checkout; the URL resolves once that SHA is on GitHub.
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
access control
AI analysis · Informational 19/100
This commit updates a dependency (cs_openalias) to a newer pinned version and adjusts automated tests to match a new requirement that every recipient record must include a 'time-to-live' (TTL) duration. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine dependency pin and test update.
The attachment images were fetched from a query-auth URL carrying the token and customer key. Now that they go through the HTTP wrapper, which logs failed requests, and dart:io puts the request URL in its exceptions, those credentials could end up in the log file.
Fetch the plain URL with the Authorization and External-Customer-Key headers instead. TorAwareNetworkImage takes the headers but keeps keying the image cache on the URL alone, so a re-mounted attachment still comes from the cache.
client.dart wasn't formatted on staging, so its diff includes one formatting change.
73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access controlcredential or privilege stateauthentication path
AI analysis · Moderate 60/100
This commit fixes a privacy/credential-leak issue in Stack Wallet's ShopinBit support-ticket feature. Previously, image attachments were downloaded using a URL that contained the user's secret access token and customer key as visible query parameters. Because the app's HTTP wrapper logs failed requests and Dart's networking exceptions include the full URL, those secret credentials could have been written to log files on the device. The patch switches to sending the credentials as HTTP headers instead, so the URL stays plain and the sensitive values are not embedded in it. A new test confirms the image loader accepts headers but still caches images by URL alone.
Lower-priorityLet ETH nodes choose Tor or clearnetby sneurlax · 827a13f0 · Oct 28, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · sneurlax
Let ETH nodes choose Tor or clearnet
The Tor/clearnet radios were hidden for Ethereum in d87af969d because web3dart could not be proxied at the time. Now that getEthClient honours the node's tor/clearnet flags and throws on a mismatch, a node stored as Tor-only or clearnet-only (older nodes, restored backups) could not be fixed from the node settings the error points the user to. Show the radios for ETH like every other coin.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Security candidateAdd Tor support for Ethereumby kroplabeskidu · d4381fb3 · Oct 27, 2026 · 5 filesMessage 78 · AdequateLow 38Details
Commit message · kroplabeskidu
Add Tor support for Ethereum
web3dart was handed a plain http Client, so ETH and ERC-20 RPC could not use Tor and the coin was flagged as not Tor-ready. Give it an IOClient wrapping a SOCKS5-proxied HttpClient instead, the same way Solana does it, and do the same for the node connection test.
Also add the usual node tor/clearnet mismatch check and set torSupport.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 38/100
This commit adds Tor privacy support for Ethereum in Stack Wallet. Previously, Ethereum RPC traffic always traveled over the regular internet (clearnet), even when the user turned on Tor, because the underlying library used a plain HTTP client. The patch routes Ethereum traffic through the Tor SOCKS5 proxy when Tor is enabled, and adds a check that warns if the selected node conflicts with the user's Tor setting. It also adds tests to confirm the proxying works.
Security candidateMark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node testby kroplabeskidu · 6d56032a · Oct 27, 2026 · 3 filesMessage 83 · StrongLow 48Details
Commit message · kroplabeskidu
Mark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node test
Nano and Banano already send every request through Tor, and Fact0rn uses the regular ElectrumX client, so they only needed the torSupport flag.
The Stellar node test proxied its first request but then created a StellarSDK with the default client, so the follow-up ledger query went out directly.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 48/100
This commit fixes a privacy leak in the Stellar wallet connection test and marks three cryptocurrencies (Nano, Banano, and Fact0rn) as supporting Tor. Previously, when testing a Stellar node, the first request went through the Tor proxy, but a follow-up request to check the ledger height was sent directly over the regular internet, potentially exposing the user's IP address and the node they were connecting to. The commit also correctly notes that Nano, Banano, and Fact0rn already supported Tor routing in practice, so their flags were updated to reflect that.
Security candidateLoad remote images over Tor when it is enabledby kroplabeskidu · 0059f656 · Oct 27, 2026 · 13 filesMessage 68 · AdequateHigh 71Details
Commit message · kroplabeskidu
Load remote images over Tor when it is enabled
Image.network and SvgPicture.network use their own HTTP clients and ignore the Tor setting, so token logos, exchange and coin logos, CakePay card images, ShopinBit attachments and theme previews were fetched directly even in Tor mode.
Add TorAwareNetworkImage and TorAwareSvgNetworkLoader, which go through the app's HTTP wrapper, and use them at all call sites.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathauthentication path
AI analysis · High 71/100
This commit fixes a privacy leak in Stack Wallet. When users turned on Tor mode to hide their internet traffic, the app was still loading remote images—such as token logos, exchange icons, gift-card pictures, and theme previews—directly over the normal internet, bypassing Tor. The change adds new image loaders that route these image requests through the app's Tor-aware HTTP client, and replaces all direct image loading calls across the wallet's user interface.
AI review queuedfix(openalias): keep the alias when a preview is repeatedby sneurlax · 9a5c8f07 · Oct 26, 2026 · 3 filesMessage 62 · AdequateLow 36Details
Commit message · sneurlax
fix(openalias): keep the alias when a preview is repeated
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 · Low 36/100
This commit fixes a bug in Stack Wallet's send flow when using OpenAlias (human-readable addresses like alice@example.com that resolve to crypto addresses). Previously, after previewing a transaction, the app replaced the alias with the resolved crypto address in the input field. If the user went back and previewed again, the app would try to re-resolve the now-plain address as if it were an alias, or lose track of the original alias. The fix keeps the alias visible to the user while internally using the resolved address for the transaction, and caches the resolution so repeated previews don't trigger unnecessary or incorrect lookups. There is no direct evidence this was exploitable for theft, but address/alias confusion in a wallet send flow is a sensitive area.
Lower-priorityfix(openalias): show one generic text for non-facade lookup errorsby sneurlax · 938961e4 · Oct 26, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · sneurlax
fix(openalias): show one generic text for non-facade lookup errors
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritydocs(openalias): say why a disconnected Tor refuses the lookupby sneurlax · 04c365f8 · Oct 26, 2026 · 1 fileMessage 74 · AdequateTriage 0Details
Commit message · sneurlax
docs(openalias): say why a disconnected Tor refuses the lookup
74/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
chore(deps): pin cs_openalias 6c9376e and dnssec_resolver b33d6a2
cs_openalias 6c9376e re-exports isOpenAliasApplication, so the application test imports the facade and openalias is no longer a dev dependency; the dependency_overrides entry stays until the package is published. dnssec_resolver b33d6a2 reports a missing record only for a secure denial, refuses SHA-1-only delegations and backs off its native polling. openalias 46d8402 and doh_transport 7211549 are unchanged.
Resolved with `flutter pub get` against the ~/.pub-cache git mirrors of github.com/cypherstack/<pkg>, each fetched from the local checkout (`git -C ~/.pub-cache/git/cache/<pkg>-<hash> fetch <checkout> +main:refs/local/main`); the URLs resolve once those SHAs are on GitHub.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
access controlsigning or wallet path
AI analysis · Low 25/100
This commit updates two internal library dependencies to newer pinned versions. The newer versions are described as tightening DNS security checks (refusing older SHA-1-only delegations and handling missing DNS records more safely) and removing a development-only dependency from the wallet's build. There is no direct evidence in the commit of an exploitable vulnerability in the wallet itself, but the dependency bumps are framed as security-hardening.
AI review queuedrefactor(openalias): share the lookup between the send viewsby sneurlax · 2ce39bf4 · Oct 26, 2026 · 4 filesMessage 62 · AdequateInformational 17Details
Commit message · sneurlax
refactor(openalias): share the lookup between the send views
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 17/100
This commit is a code cleanup that moves the OpenAlias lookup logic into a shared service so both the mobile and desktop send screens use the same implementation. There is no direct evidence in the commit that it fixes a security vulnerability; it appears to be a refactoring change with added unit tests.
Lower-priorityupdate ios xcode project with swiftpmby Julian · 292c895f · Oct 26, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Julian
update ios xcode project with swiftpm
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Merge pull request #1475 from slopbot9k/rust-1.99.1
Require Rust 1.99.1 and pin the plugin releases built with it
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlmerge-commit duplicate discount
AI analysis · Informational 12/100
This commit updates the Rust compiler version used to build the wallet from 1.89.0 to 1.99.1 across build scripts, documentation, and dependency references. It also switches some third-party plugin references to newer commits or forks maintained by the same team, and updates prebuilt binary download URLs and SHA256 hashes. A small code change removes a `disable()` call before stopping the Tor service. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine toolchain and dependency refresh.
AI review queuedFormat Tor templateby slopbot9k · 6cb1d36c · Oct 26, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · slopbot9k
Format Tor template
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 adds a single blank line to a code template file. It is purely a formatting change with no functional or security impact.
Security candidateMerge branch 'staging' into rust-1.99.1by Julian · c7ef7391 · Oct 26, 2026 · 8 filesMessage 45 · ThinLow 33Details
Commit message · Julian
Merge branch 'staging' into rust-1.99.1
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 33/100
This commit is a routine merge that mostly improves how Stack Wallet's Linux release packages are built. The main change adds a build-time script that strips an unsafe 'executable stack' flag from three cryptocurrency wallet libraries (Monero, Wownero, Salvium) so modern Linux systems will load them. It also updates Dogecoin and Litecoin block-explorer URLs from an old domain to a new one. There is no evidence in the commit of an active security vulnerability being exploited, but the executable-stack flag is a genuine hardening concern for Linux binaries.