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.
This commit removes a former Monero maintainer's GPG key from the list of trusted keys used by the GUI wallet's automatic updater. It is a routine trust-list cleanup after a maintainer left the project, not a fix for an active security fla…
Removal of a trusted GPG key from the software-update trust anchor setChange affects the built-in GUI updater's maintainer verification list
This commit adds a new command-line option --ssl-check and runs it in CI. The check makes a simple HTTPS request to the Monero website to confirm SSL/TLS certificate validation is working in the build. It is a testing/diagnostic addition, …
Adds SSL/TLS connectivity self-testUnsets SSL_CERT_FILE/SSL_CERT_DIR in CI to test default certificate validation pathHidden CLI option not exposed in help
This commit changes the macOS build instructions to install a specific, pinned version of OpenSSL (version 3) rather than whatever the latest version happens to be. It also tells the build system exactly where that pinned version is locate…
Pins a critical cryptographic dependency (OpenSSL) to a known major versionAdds explicit OPENSSL_ROOT_DIR to prevent CMake from picking up an unintended OpenSSL installationReduces supply-chain risk from unpinned Homebrew formula updates
This merge changes how text is shown in the Monero GUI wallet. The main goal appears to be preventing rich-text formatting (HTML-like markup) from being interpreted in places where untrusted data could appear, such as scanned QR codes, dia…
Multiple QML text elements switched from AutoText/default to Text.PlainTextStandardDialog content area defaulted to TextEdit.PlainText instead of TextEdit.AutoTextQRCodeScanner removed MessageDialog usage and routes errors through informationPopup
This commit adds a new automated test that runs in the project's continuous integration (CI) pipeline. The test launches the Monero GUI wallet with a hidden '--ssl-check' flag, which tries to download a small file over HTTPS from the offic…
New hidden CLI flag added for SSL/TLS connectivity validationCI runs SSL check against real external endpoint (web.getmonero.org)Environment variables SSL_CERT_FILE and SSL_CERT_DIR are explicitly unset during CI test to ensure bundled certificates are used
This commit changes the macOS build instructions in an automated workflow so that the build explicitly uses OpenSSL version 3 instead of whatever version Homebrew currently provides by default. It is a build-hardening change, not a fix for…
Dependency version pinning in CI/CD workflowExplicit OPENSSL_ROOT_DIR to avoid picking up a different OpenSSL installationBuild reproducibility / supply-chain hardening
This is a small user-interface improvement for the Monero GUI wallet. When a user checks a 'reserve proof' (a cryptographic receipt showing how much Monero an address holds), the result popup now also shows the unspent amount. The code als…
No security-relevant signal: UI-only change adding an unspent amount label to reserve proof checksDefensive initialization of local output variables (good=false, total=0, spent=0), which is good practice but not a fix for an observed bug
This update fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might have accepted a revoked (cancelled) subkey, or used an older signature that allowed signing even when a newer one did not. The patch now rejects…
OpenPGP subkey revocation not previously enforcedBinding signature selection did not consider creation time, allowing stale signing-capable signatures to override newer non-signing onesMarker/Trust packets now skipped without terminating subkey signature sequence
This commit updates the Monero GUI's message/file signing feature so users can now sign with any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer error messages…
Signing now bound to a user-selected wallet address/subaddress, reducing risk of signing under an unintended primary addressHardware-backed and view-only wallets are explicitly prevented from signing in the UIError handling added for failed sign operations
This is a user-interface performance patch for the Monero wallet app. It rewrites how the Account and Receive pages display long lists of subaddresses, replacing a layout that loaded every item at once with a scrollable list that reuses it…
No direct security signal in diff: no cryptographic, network, or wallet-seed handling changesOne defensive guard added: bounds check on subaddressListView.currentIndex before accessing wallet subaddress dataOne variable rename fixes a typo but has no security effect
This commit is a minor user-interface improvement for the Monero GUI wallet. When a user checks a 'reserve proof' (a cryptographic attestation about how much Monero is held and spent), the result dialog now also shows the 'unspent' amount.…
This change fixes how the Monero GUI reads OpenPGP public keys. Previously, the software might accept a revoked (cancelled) subkey or use an older signature that allowed signing even when a newer one did not. After the patch, revoked subke…
OpenPGP subkey revocation now enforcedBinding signature selection changed from first-match to newest-by-creation-timeMarker and Trust packets now explicitly skipped without terminating subkey signature sequence
This commit changes how the Monero wallet's user interface displays text that comes from outside sources. It switches several labels and dialogs from rich text (which can include formatting, links, or hidden instructions) to plain text, re…
Multiple QML text elements switched from AutoText/RichText-capable defaults to Text.PlainTextStandardDialog default textFormat changed from TextEdit.AutoText to TextEdit.PlainTextQR scanner MessageDialog removed; scanned data errors now shown through a controlled popup as plain text
This commit updates the Monero GUI wallet's signing feature so users can now sign messages and files using any wallet subaddress, not just the main address. It also disables signing for hardware-backed and view-only wallets, shows clearer …
Signing UI now disabled for hardware-backed wallets (isHwBacked) and view-only wallets (viewOnly)Backend error strings are now displayed to the user instead of silently failingForeign / non-wallet addresses are rejected by the underlying wallet implementation and produce an error dialog
This commit only updates the version pointer of an embedded dependency called 'quirc' (a QR-code decoding library) inside the Monero GUI repository. The actual code changes are not shown in the diff because the dependency is stored as a se…
This change tightens how the Monero GUI wallet handles its network proxy settings. Previously, the wallet's proxy address could be changed from many places in the app, which could let a bug or malicious UI flow silently switch traffic to a…
Removal of writable proxy address setter reduces attack surface for proxy misconfigurationCentralizes proxy reconnection logic in a single helper functionPrevents QML binding from silently overriding proxy address
This change hardens how the Monero GUI opens a printable PDF seed template. Previously, the app copied a bundled PDF to a predictable temporary path and opened it without checking whether the file had been tampered with. Now it creates a p…
Local file integrity verification added (SHA-256) before opening an embedded PDFPredictable temporary file path replaced with QTemporaryDir unique directoryReturn-value handling added so QML can surface verification failures to the user
This patch fixes a user-interface freeze in the Monero GUI wallet when using the 'sweep unmixable outputs' feature. The old code called a synchronous (blocking) function that could hang the interface; the new code uses an asynchronous call…
UI freeze / denial-of-service to the local user when sweeping unmixable outputsObject lifetime change in PendingTransaction parent assignmentNo input validation, cryptographic, or network security changes visible
This commit is a large cleanup and hardening of the OpenPGP signature verification code used by the Monero GUI's automatic updater. It adds stricter parsing of armored PGP data, validates armor headers and checksums, rejects unexpected sig…
Custom cryptographic code was significantly hardenedSignature verification now rejects unsupported signature typesArmor parsing now validates headers, tails, base64 alphabet, and CRC24
This commit is a user-interface cleanup, not a security fix. It moves the existing password-strength meter into a reusable component and adds it to the password-change dialog. The actual password-strength calculation is still performed by …
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedTransactionHistoryModel: only place pending tx firstby selsta · 27328f36 · Sep 2, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · selsta
TransactionHistoryModel: only place pending tx first
50/100 · ThinMessage clarity
✓ Specific, 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 19/100
This commit fixes a display bug in the Monero GUI wallet's transaction history list. Previously, failed transactions were being shown at the top of the list alongside pending transactions, because any transaction without a confirmed block height was treated as 'top priority.' Now only genuinely pending transactions are promoted to the top; failed transactions are sorted by their actual (zero) block height instead. There is no direct security risk such as theft, code execution, or data loss.
AI review queuedHistory: improve display of transactions with multiple recipientsby selsta · a3dc3882 · Sep 2, 2026 · 5 filesMessage 50 · ThinInformational 15Details
Commit message · selsta
History: improve display of transactions with multiple recipients
50/100 · ThinMessage clarity
✓ Specific, 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 15/100
This commit is a user-interface improvement for the Monero GUI wallet's transaction history screen. It changes how outgoing payments to multiple recipients are displayed, searched, and copied. There is no security vulnerability here; it is purely a usability enhancement.
Wallet: fix send confirmation stale transaction race
50/100 · ThinMessage clarity
✓ Specific, 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 · Low 42/100
This patch fixes a race condition in the Monero GUI wallet's send screen. If a user quickly changed send details or canceled a transaction while an earlier transaction was still being prepared in the background, the wallet could mix up the old and new transactions. The fix tags each send request with an ID and discards results from outdated requests, and it properly cleans up canceled transactions to avoid memory leaks or accidental use of the wrong transaction.
This is a routine GitHub Actions CI fix for the Windows build. It adds the 'rust:p' package to the list of MSYS2 packages installed during the build. There is no security-relevant change visible in the diff.
Lower-prioritymain: make socks5 proxy flag override saved settingby selsta · e68aac12 · Aug 23, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · selsta
main: make socks5 proxy flag override saved setting
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateupdater: use proxy for signed hash downloadsby selsta · 5e5ea68f · Aug 23, 2026 · 7 filesMessage 45 · ThinModerate 59Details
Commit message · selsta
updater: use proxy for signed hash downloads
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Moderate 59/100
This change fixes a privacy leak in the Monero GUI wallet's update checker. Previously, when the wallet checked for updates and downloaded the signed list of official file hashes, it did not route that request through the user's configured proxy. This could expose the user's real IP address to the update server and any network observer, even if the user had set a proxy for other wallet traffic. The patch now passes the configured proxy address through to the update check so those hash downloads also go through the proxy.
Lower-prioritycmake: add option to skip compilation of optional monero binariesby jpk68 · dcb8ec03 · Aug 11, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · jpk68
cmake: add option to skip compilation of optional monero binaries
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedp2pool v4.18by SChernykh · ddd080e3 · Aug 5, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · SChernykh
p2pool v4.18
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 simply updates the Monero GUI's built-in downloader to fetch a newer version (4.18) of the bundled P2Pool mining software. It changes download URLs and the expected file hashes to match the new release. There is no indication of a security fix or vulnerability in this change.
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityqml: fix restore height from a date typed without hyphensby munzzyy · 2e99db88 · Aug 3, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · munzzyy
qml: fix restore height from a date typed without hyphens
The restore height field accepts a wallet creation date, and there is a fallback that catches the date typed as 20201225 instead of 2020-12-25. That fallback is gated on the year being between 2014 and a hardcoded 2025, so since January it does nothing: 20260315 falls through to parseInt and becomes restore height 20260315, far past the current tip. The wallet then scans nothing and shows an empty balance, with no error to explain it.
Compare against the current year instead of a fixed one. Reaches the same three call sites (restore wizard, hardware device wizard, and Settings > Info > change restore height) and adds a QML test for the function.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Transfer: disable offline signing for hardware wallets
Reported by zkao, a tool by zkSecurity
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Moderate 58/100
This commit removes the 'Sign (offline)' button for hardware wallets in the Monero GUI wallet. The change prevents users from attempting an unsupported operation that could lead to failed or unsafe transactions when using a Ledger/Trezor-like device. The issue was reported by zkao using a tool from zkSecurity, suggesting it was found during a security review, but the commit message does not explain the exact attack or failure scenario.
Lower-prioritymain: hint at device state when a hardware wallet fails to openby reservedbytes · f43b7e59 · Jul 29, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · reservedbytes
main: hint at device state when a hardware wallet fails to open
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
✓ 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 15/100
This commit is a straightforward user-interface cleanup in the Monero wallet restore wizard. It replaces a third radio-button option ('Restore from QR Code') with a dedicated QR scan button, simplifying the layout. There is no security-relevant change in behavior—QR scanning still works the same way, and no sensitive data handling or access-control logic was modified.
AI review queuedwizard: support key-based monero-wallet restore QR codesby selsta · a33f2421 · Jul 21, 2026 · 3 filesMessage 50 · ThinLow 27Details
Commit message · selsta
wizard: support key-based monero-wallet restore QR codes
50/100 · ThinMessage clarity
✓ Specific, 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 · Low 27/100
This commit adds a feature to the Monero GUI wallet that lets users scan a QR code to restore a wallet from its secret keys. The change itself is a feature addition, not a direct security fix. However, it handles extremely sensitive data (private view and spend keys) encoded in QR codes, and the parsing logic uses string operations and URI decoding that could be risky if a malformed or malicious QR code is scanned. There is no evidence in the commit of input validation beyond checking the public address format. Because private keys are involved, any weakness in parsing could have serious consequences, but the commit does not demonstrate an actual vulnerability.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedwizard: fix restore from QR codeby Thomas · fbe4c084 · Jul 19, 2026 · 2 filesMessage 68 · AdequateInformational 23Details
Commit message · Thomas
wizard: fix restore from QR code
updateFromQrCode lived in Wizard.js, a .pragma library script with no access to QML scope, so every scan aborted on its first statement and filled nothing. Broken since the wizard redesign (f329a710); the function also still referenced pre-redesign items that no longer exist.
Move it into WizardRestoreWallet1.qml next to the fields it fills, switch to the keys form so the scanned values are visible, and handle the null extra_parameters emitted for bare-address QR codes.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This commit fixes a broken feature in the Monero wallet's setup wizard that restores a wallet by scanning a QR code. The feature had been completely non-functional since a prior redesign because the code that processes the scanned QR code was placed in a JavaScript library that cannot access the wizard's user-interface elements. The patch moves that code into the correct wizard page, updates it to use the current user-interface elements, and safely handles QR codes that contain only an address with no extra key data. This is a straightforward bug fix with no clear security relevance.
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds automated user-interface tests for the Monero wallet setup wizard. It does not change how real users create or open wallets; it only adds test code and exposes a few internal UI control names so the tests can interact with wizard pages. There is no security fix or vulnerability here.
Also show the wallet location selector in all wallet modes and use the selected path when creating a wallet.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 24/100
This commit changes the Monero GUI wallet creation wizard so that users always see and can edit the wallet save location, regardless of which wallet mode they chose. Previously, the location field was hidden in simpler modes and the wallet was saved to a default folder. The change also stops validating whether the default folder is writable, only checking custom locations. This is a user-experience and correctness fix rather than a clear security patch, though it removes a minor validation inconsistency.
Receive: fix stale subaddress selection after switching accounts
subaddressListView.currentIndex was only reset when it equaled -1 (the initial sentinel), so switching to an account with fewer addresses left the Receive page showing the old index and its label while the QR/address itself already reflected the new account's primary address. onPageCompleted also hardcoded index 0 when setting current_address instead of using the selected index, so the shown address could disagree with the selected row's label even within the same account after revisiting the page.
Validate currentIndex against the current account's address count on page load, and share the address/label sync logic between the selection handler and onPageCompleted so both stay consistent.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validationprivacy or spend-authorization protocol
AI analysis · Low 25/100
This is a user-interface bug fix in the Monero wallet's Receive page. When a user switched between accounts, the page could show a label and QR code from one account while the displayed address belonged to another account, because the selected list row was not updated to match the new account. The fix makes sure the selected row and displayed address/label stay in sync. It is a consistency bug, not a cryptographic or network vulnerability.
✓ 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 · Moderate 59/100
This change alters the Monero GUI wallet setup wizard so that newly created or recovered wallets are kept only in memory, rather than being written to a temporary file on disk during the setup process. The old approach created temporary wallet files on the computer's storage and then deleted them after the user finished the wizard. The patch removes the code that created and cleaned up those temporary files. This is a defensive improvement: it reduces the chance that an unfinished or temporary wallet file containing sensitive data is left behind on disk, exposed to other users, recovered by forensic tools, or leaked through backups, swap files, or file indexing. The change also adds a small UI guard so the wizard cannot be interacted with while a hardware-device wallet is being created asynchronously.
AI review queuedworkflows: drop requests dependency from p2pool hash verificationby Thomas · 0575b7d6 · Jul 15, 2026 · 1 fileMessage 83 · StrongInformational 21Details
Commit message · Thomas
workflows: drop requests dependency from p2pool hash verification
857f0bc6 moved the p2pool-hashes job to the ubuntu-slim runner, which does not ship the requests module, so the check fails with ModuleNotFoundError for every pull request touching P2PoolManager.cpp. Use urllib from the standard library for the single API call instead.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
This commit fixes a broken GitHub workflow script that verifies P2Pool software hashes. The script previously used the third-party 'requests' library, which is not installed on the slim Ubuntu runner used by the project. The change switches to Python's built-in 'urllib' library so the automated check can run again. It is a reliability/maintenance fix, not a security vulnerability patch.