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.
53/100 average clarity
30Strong · 80–100
77Adequate · 60–79
108Thin · 40–59
70Opaque · 0–39
46security candidates with opaque commit messaging
This commit adds security checks to SeedSigner, an offline Bitcoin signing device, to prevent malicious or buggy wallet software from tricking users into sending change to derivation paths their wallet will never scan. It now verifies that…
New fatal error class PSBTChangeDerivationPathError for non-standard change derivation pathsNew fatal error class PSBTUnverifiableMixedInputBasePathsError for unverifiable mixed-base-path segwit v0 inputsChange output base path must match a verified input base path
This commit hardens SeedSigner's PSBT (Bitcoin transaction) parser so it no longer trusts a coordinator's claim that an input belongs to your seed. Before, the device only checked that your seed could derive the claimed key. Now it also re…
New attack-level exception: PSBTInputOwnershipContradictionError when an input claims the seed's key but the committed script does not use itInput ownership now verified by rebuilding the scriptPubKey from the claimed key rather than trusting PSBT bip32 derivationsTaproot key-path spends verified by re-applying the merkle-root tweak to the internal key and comparing to the committed output
This commit fixes a security flaw in SeedSigner, a small hardware wallet used to sign Bitcoin transactions. The bug could let a malicious transaction coordinator trick the device into accepting change money sent to a wallet path the user n…
New security check explicitly described as preventing a malicious coordinator from anchoring change to an unmonitored derivation pathNew exception class PSBTUnverifiableMixedInputBasePathsError with Warning-grade refusalUI flow now redirects to a blocking warning screen instead of allowing signing
This commit fixes a security check in SeedSigner, a small hardware-wallet-like device used to sign Bitcoin transactions. Previously, when deciding whether a change output's address was suspiciously far from the user's known addresses, the …
Fixes a window-widening attack against change-output verificationChange-output address index check now uses smallest input index instead of largestAdds hardened-input edge-case handling (window measured from 0)
This commit only adds a new test case to the project's test suite. It does not change any production code. The new test checks that the existing PSBT parser correctly rejects a specific kind of suspicious change output (one placed at a dee…
Adds defensive test coverage for PSBT change-output derivation-path validationRelates to preventing a coordinator with an account xpub from routing change to an unexpected deeper path
This commit adds a safety check to SeedSigner that refuses to sign a Bitcoin transaction if the change output is being sent to a derivation path the user's wallet is unlikely to scan. Before this change, an attacker could trick a user into…
New attack-level exception PSBTChangeDerivationPathError for change sent to an unscanned derivation pathNew warning WARNING__CHANGE_ADDRESS_INDEX_BEYOND_WINDOW for change address indices far past spent indicesNew UI screen PSBTUnexpectedChangeDerivationPathView with DireWarningScreen and forced discard
This commit is a code cleanup, not a security fix. It consolidates several warning screens shown before signing a Bitcoin transaction into a single reusable view. The warnings themselves—such as 'high fee' and 'no change'—still behave the …
Refactor only: no change to validation, cryptography, or signing logicUser-facing warning text and flow remain equivalentAdds unit tests covering high-fee, no-change, and combined warning sequences
This commit only reorganizes test code. It adds a helper function that replaces twelve nearly identical blocks of test setup code, with no changes to the actual wallet or signing logic that users rely on.
This commit only moves and rewrites documentation comments inside the code. It does not change how the program behaves, what it checks, or how it responds to malicious data. The logic for detecting and holding security findings in PSBT par…
This commit adds security checks to SeedSigner, a small offline Bitcoin signing device. Before the change, a malicious or buggy wallet coordinator could give the device a transaction where an input's hidden script did not match the public …
New validation logic compares supplied witness/redeem scripts against scriptPubKey hashesNew exception classes explicitly label script mismatch as an attack and missing/extraneous scripts as correctness problemsUI flow terminates signing before rendering transaction details when a script check fails
This commit simply adds Swahili as a new language option in the SeedSigner settings. It is a localization (translation) change with no security relevance.
This commit fixes how SeedSigner reads the extra data attached to OP_RETURN Bitcoin transaction outputs. Previously the code always assumed the data was introduced by OP_PUSHDATA1, which meant it would misread or crash on the more common d…
Fixes incorrect parsing of OP_RETURN data due to assumed push opcodeAdds robust handling for direct push, OP_PUSHDATA1/2/4, and OP_0-OP_16Introduces explicit malformed-script rejection instead of silent mis-parsing
This update makes SeedSigner refuse Bitcoin transaction files (PSBTs) where the outgoing amounts are larger than the incoming amounts. Before the fix, the device would have accepted such impossible transactions and shown the user a negativ…
Input validation: rejects PSBTs with mathematically impossible fee valuesUser-facing safeguard: prevents confusing negative fee from reaching transaction review screensNew exception class with clear semantics (PSBTNegativeFeeError)
This commit only updates a code comment to remove an outdated claim. The actual security check for negative fees remains unchanged, and a prior code change already verifies input amounts before outputs are parsed. There is no functional se…
This commit fixes a security flaw in SeedSigner, a small offline Bitcoin signing device. Previously, when a user scanned a transaction to sign, the device added up the input amounts exactly as a malicious or compromised computer/coordinato…
Fixes a fee-display manipulation vulnerability where a compromised coordinator could understate input amounts to hide excessive real feesAdds explicit verification of each input's amount against the prior transaction before totaling inputsRaises dedicated security exceptions (PSBTInputAmountVerificationError, PSBTMissingInputUtxoError) and blocks the signing flow
This commit only rewrites the explanatory text (docstrings) inside test code. No actual program logic, security checks, or test behavior changed. It is a documentation cleanup within tests.
This commit only changes test code. It tightens some Python assertions (using 'is False' instead of '== False') and expands one test to run across more test fixtures. There is no change to the actual wallet or PSBT parsing logic that users…
This commit only changes a test file. It removes a small helper method called parse() and replaces its calls with the same one-line PSBTParser constructor call written out directly. There is no change to the actual wallet/security code tha…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedbugfixby kdmukai · 8cbf69d4 · Dec 24, 2025 · 1 fileMessage 0 · OpaqueInformational 18Details
Commit message · kdmukai
bugfix
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100
This is a one-line bugfix in a test helper script that generates screenshots. The change swaps a public method call for directly clearing an internal singleton variable. It only affects the screenshot generator's cleanup routine and does not appear to be a security fix for user-facing code.
AI review queuedCI bugfixby kdmukai · b01de936 · Dec 24, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · kdmukai
CI bugfix
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes a test file that checks how the software reports its version number when running inside GitHub Actions. It does not change the actual version-detection code or any security-sensitive behavior. There is no security issue here.
AI review queuedtest bugfixesby kdmukai · 70f86d09 · Dec 24, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
test bugfixes
28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes test code in tests/test_version.py. It fixes test bugs by adding a fixture that controls an environment variable during tests and updates several test assertions to call the correct utility class (VersionUtils instead of Version). There are no changes to the actual application code that users run, so this has no direct security impact on the SeedSigner device or software.
AI review queuedFix "skip test" callby kdmukai · b1877e64 · Dec 20, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · kdmukai
Fix "skip test" call
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit fixes a minor test-only bug. The test file was calling a unittest method (self.skipTest) inside a pytest-based test, which does not work correctly. The change replaces it with pytest.skip and adjusts imports. It only affects how one test is skipped when there is no Git directory; it does not change any production code or security behavior.
AI review queuedCorrecting assert mistakeby biel · a1e47eb8 · Dec 19, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · biel
Correcting assert mistake
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a one-line correction in a test file. The test was checking that a 'passphrase' setting was NOT included in parsed QR-code settings, but the intended behavior is that it SHOULD be included. The change fixes the test assertion to match the actual expected behavior. It does not change any production code and has no direct security impact on users.
AI review queuedChanging testsby biel · 02f9b8c9 · Dec 17, 2025 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · biel
Changing tests
Change tests
Correcting tests
28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates test files to remove references to an obsolete 'xpub_export' setting. It does not change any production code, user-facing behavior, or security controls. There is no security issue in this patch.
AI review queuedFix multisig testsby alvroble · 386ecdc3 · Dec 9, 2025 · 1 fileMessage 38 · OpaqueInformational 12Details
Commit message · alvroble
Fix multisig tests
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit only changes test code. It updates a unit test so that it checks both single-signature and multi-signature PSBT inputs, and it makes the fingerprint assertions more precise by distinguishing public keys that belong to the current seed from those that don't. There is no change to the actual application code that handles seeds or transactions.
AI review queuedImprovement of tests, single-sig isolation * Better naming and code efficiency * Removed multisig from test inputs until figured outby alvroble · 0e4da284 · Dec 8, 2025 · 1 fileMessage 83 · StrongInformational 12Details
Commit message · alvroble
Improvement of tests, single-sig isolation * Better naming and code efficiency * Removed multisig from test inputs until figured out
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
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit only changes a test file. It renames a test, tightens some assertions, and temporarily removes multisig test cases from a loop so only single-signature inputs are exercised. There is no change to the actual PSBT parsing or wallet code, so it does not fix or introduce a security issue by itself.
AI review queuedUpdates test suiteby alvroble · 21bf4e8e · Oct 24, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · alvroble
Updates test suite
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only updates the project's test suite. It adds a new screenshot configuration for a warning screen and adds one new assertion checking a default setting value. There are no changes to production code, no security fixes, and no behavior changes that affect users.
AI review queuedremove unused importby kdmukai · 7a054a05 · Oct 23, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
remove unused import
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit removes an unused test import (UnhandledExceptionView) from a test helper file. It is a routine cleanup with no security relevance.
AI review queuedAdd test case test_zero_fingerprint_handlingby alvroble · 8ea3c42f · Oct 2, 2025 · 1 fileMessage 45 · ThinInformational 12Details
Commit message · alvroble
Add test case test_zero_fingerprint_handling
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit only adds a new automated test to the project. It does not change any production code, so by itself it cannot introduce a security vulnerability or fix one. The test checks that the software can correctly handle PSBT files where wallet fingerprints are all zeros, which can happen when a wallet is created from an extended public key (XPUB) without a full derivation path. The test verifies the software can match the public keys against the seed and fill in the correct fingerprint.
AI review queuedremove unnecessary blank lineby kdmukai · ac194d07 · Aug 26, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · kdmukai
remove unnecessary blank line
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit removes a single blank line from a test screenshot generator script. It is a cosmetic code cleanup with no functional, security, or behavioral change.