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 queuedTest change at an extra level under the base pathby kdmukai · 9c19e9d6 · Oct 30, 2026 · 1 fileMessage 78 · AdequateInformational 12Details
Commit message · kdmukai
Test change at an extra level under the base path
The base path rule compares base paths for equality. Its test covered only a base path that differs from the input's in its last level, so a prefix comparison would still pass it while accepting change at an extra level under the input's base path. A coordinator holding the account xpub can build that change. The test now covers both variants, on every supported script type.
78/100 · AdequateMessage clarity
✓ 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 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 deeper derivation path than expected). Because no actual parser logic is modified, this commit by itself does not fix or introduce a security vulnerability.
AI review queuedAdd a test helper to set an input's locking scriptby kdmukai · b297c869 · Oct 30, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · kdmukai
Add a test helper to set an input's locking script
Twelve places in the tests changed an input's scriptPubKey and then dropped its non_witness_utxo, each with its own comment on why. The previous transaction still pays the old scriptPubKey, and editing it to match would change its txid, so the drop is required. set_input_locking_script does both and explains it once.
The bare multisig test keeps its own edit: that input is not segwit, so the helper's witness-only reasoning does not hold there.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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.
AI review queuedTrim the input-amount verification test docstringsby newtonick · afb7305a · Oct 20, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · newtonick
Trim the input-amount verification test docstrings
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathparser or protocol pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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.
AI review queuedTighten the input-amount test asserts and run the no-utxo test over every fixtureby newtonick · 222bf3d5 · Oct 20, 2026 · 1 fileMessage 60 · AdequateInformational 12Details
Commit message · newtonick
Tighten the input-amount test asserts and run the no-utxo test over every fixture
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ 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 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 rely on, so it does not fix or introduce a security issue in the product itself.
AI review queuedcorrect indentationby newtonick · ee853c39 · Oct 20, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · newtonick
correct indentation
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! 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 15/100
This commit only fixes the indentation of comments and code inside a single test file. No real program logic, security behavior, or user-facing code was changed. It is a cosmetic/test-only formatting correction.
AI review queuedApply suggestion from @kdmukaiby Nick Klockenga · d4acbf34 · Oct 20, 2026 · 1 fileMessage 50 · ThinInformational 11Details
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 11/100
This commit only changes a test file. It updates how one test case sets up its test data to match a previous code change, based on a review suggestion. There is no change to the actual application code that users run, so it does not create or fix a security issue in the product itself.
AI review queuedApply suggestion from @kdmukaiby Nick Klockenga · ec511361 · Oct 20, 2026 · 1 fileMessage 50 · ThinInformational 15Details
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes comments and the order of two lines in a test file. It does not alter any actual code behavior, security logic, or production functionality. It is a code-review cleanup suggestion applied to a unit test.
AI review queuedApply suggestion from @kdmukaiby Nick Klockenga · 34b881a3 · Oct 20, 2026 · 1 fileMessage 50 · ThinInformational 12Details
✓ Descriptive subject✓ Provides an 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 rewrites a comment in a test file. It does not change any actual code behavior, security checks, or user-facing functionality. The new comment explains why a test expects an error when a legacy Bitcoin transaction input only provides a witness UTXO. There is no security fix or vulnerability introduced here.
✓ Subject identifies a change! 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 15/100
This commit fixes a single typo in a comment inside a test file. It changes 'Prep the our modified psbt in embit' to 'Prep the modified psbt in embit'. There is no code, logic, or security change whatsoever.
AI review queuedTighten the derivation cache guard testsby kdmukai · 65b1d3d9 · Aug 15, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · kdmukai
Tighten the derivation cache guard tests
The class docstring enumerated two claims while the class held six tests, and each test already documents its own claim, so state the purpose instead of maintaining a second copy.
test_get_cosigners_identical_with_and_without_cache only ever wrote to the cache: its three cosigners sit below distinct parent xpubs, so all six level lookups missed and nothing was read back. Call _get_cosigners a third time against the populated cache so the comparison covers the read path, which is where a wrong key would surface.
Move the two assert messages that restated their own expressions into comments that give the reason instead.
78/100 · AdequateMessage clarity
✓ 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 15/100
This commit only changes test code. It tightens an existing unit test so it actually exercises the cache read path, and improves comments and docstrings. No production code was modified, so it cannot introduce or fix a security vulnerability in the application itself.
AI review queuedRecord cache sizes during the parse, not after itby kdmukai · 448e0eb6 · Aug 14, 2026 · 1 fileMessage 78 · AdequateInformational 15Details
Commit message · kdmukai
Record cache sizes during the parse, not after it
Reading the cache dict back once the parse is over depends on the parse leaving that dict intact, which is an implementation detail rather than the guarantee under test.
78/100 · AdequateMessage clarity
✓ 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 15/100
This commit only changes a test file. It makes the test measure the size of a temporary cache while the code is running, instead of reading the cache afterward. This is a test-quality improvement, not a security fix.
AI review queuedFix CI crash in screenshot generator when latest-release fetch failsby kdmukai · a6dfb0cd · Aug 9, 2026 · 1 fileMessage 73 · AdequateInformational 17Details
Commit message · kdmukai
Fix CI crash in screenshot generator when latest-release fetch fails
The screenshot generator fetches the latest release tag at import time via an unauthenticated GitHub API call. GitHub-hosted runners share outbound IPs and the unauthenticated api.github.com limit is 60 req/hr/IP, so the call was intermittently rate-limited (HTTP 403), returned (None, None), and fed None into the mock_version_to_most_recent_release Version mock. That crashed rendering for every locale with "TypeError: 'NoneType' object is not subscriptable" in the OpeningSplash version string (and would likewise hit len(None) on the Version settings screen).
Substitute a placeholder version name and timestamp when the fetch can't resolve the latest release, so the "release build" screenshots still render instead of feeding None into the mock. The real fetch is unchanged when it succeeds.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 17/100
This is a test-only fix for a CI screenshot generator. It stops the test suite from crashing when GitHub's public API rate-limits an unauthenticated version-lookup request. There is no security vulnerability in the actual SeedSigner wallet or user-facing code; the change only adds a fallback placeholder so screenshots keep rendering during automated tests.
AI review queuedImprove tests, maintainabilityby kdmukai · e9b08094 · Feb 17, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai
Improve tests, maintainability
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes test files. It refactors how SettingsQR test data is built by introducing a shared base class so tests use the current default settings automatically instead of hardcoded strings. There is no change to the actual application code that users run, so it cannot directly affect security or introduce a vulnerability.
AI review queuedUpdate PR templateby kdmukai · b386caa8 · Feb 14, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
Update PR template
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit only updates the GitHub pull request template, which is a form contributors fill out when submitting code changes. It does not change any actual application code, so it has no direct security impact on the SeedSigner software or its users.
AI review queuedRestore whitespace alignment formattingby kdmukai · b447edd6 · Jan 20, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · kdmukai
Restore whitespace alignment formatting
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 only adjusts whitespace in a test screenshot generator file so that the opening parentheses line up visually. No code behavior, logic, or security-sensitive content changed.
AI review queuedMinor comments updatesby kdmukai · fd051d3b · Jan 20, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
Minor comments updates
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 only rewords comments in two test helper files. No code behavior was changed, so it has no security relevance.
AI review queuedMinor test improvementby kdmukai · a8e68142 · Jan 20, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · kdmukai
Minor test improvement
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 adds one extra test case (an empty list `[]`) to an existing unit test that checks how the SeedSigner settings code handles empty values. It is purely a test-file change and does not modify any production code, user-facing behavior, or security-sensitive logic.
AI review queuedMinor cleanupby kdmukai · f639d3df · Jan 20, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · kdmukai
Minor cleanup
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 a trivial cleanup of a test file. It removes an unused import (SettingsEntry), deletes a debug print statement, and fixes some whitespace. There is no change to the actual application code that handles seeds, keys, or user settings, so it has no security relevance.
AI review queuedCleanupby kdmukai · 45d75ea3 · Dec 27, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · kdmukai
Cleanup
0/100 · OpaqueMessage clarity
! Generic or placeholder 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 removes a helper function used only in a screenshot-generation test script. The deleted code fetched the latest SeedSigner release version from GitHub and temporarily overwrote version data so screenshots would display consistent version information. It is a test-only cleanup with no effect on the actual SeedSigner application or its security.
AI review queuedMinor comments updatesby kdmukai · fc6fa4f5 · Dec 27, 2025 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
Minor comments updates
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 only rewords comments and docstrings in test helper files that generate screenshots. No code behavior was changed, so it has no security relevance.
AI review queuedCI env var fixby kdmukai · 8ce89710 · Dec 26, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
CI env var fix
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit moves a GitHub Actions environment variable definition from inside a single test step to the top of the workflow file. It is a routine CI configuration cleanup with no apparent security relevance.
AI review queuedGithub Actions CI bugfixby kdmukai · e7da2e98 · Dec 26, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
Github Actions CI bugfix
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 only updates a test file to match how GitHub Actions environment variables are named. It does not change the actual application code that users run, and there is no security issue visible here.
AI review queuedRemove unnecessary patchby kdmukai · 075d66a6 · Dec 26, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
Remove unnecessary patch
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 a temporary workaround (mocking the operating system type) from a single automated test file. It does not change any production code, user-facing behavior, or security-sensitive logic. The change simply makes the test rely on the real environment instead of pretending to be a specific OS.
AI review queuedMinor refactorby kdmukai · eed16f73 · Dec 25, 2025 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · kdmukai
Minor refactor
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 is a tiny code cleanup in a helper script that writes a version information file. It removes four comment lines and combines two variable assignments into one line. There is no functional change and no security relevance.
AI review queuedbugfix after renameby kdmukai · c475b8f7 · Dec 25, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai
bugfix after rename
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 is a one-line bugfix in a build helper script. A previous code rename left a reference to an old method name, which would have caused the script to crash. The patch simply points the script to the correct new method name. There is no security-relevant change visible in the diff.