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.
Security candidateMerge pull request #750 from alvroble/bugfix/toast_timing_issueby Nick Klockenga · 9662970c · Oct 20, 2025 · 336 filesMessage 73 · AdequateInformational 15Details
Commit message · Nick Klockenga
Merge pull request #750 from alvroble/bugfix/toast_timing_issue
[Bugfix] Remove unnecessary sleep time in `toast.py` to speed up Screenshot Generator
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
seed or entropy pathsigning or wallet pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large repository merge that primarily adds documentation, build workflows, enclosure files, and project scaffolding. The only code change described in the title is a minor bugfix in toast.py that removes an unnecessary sleep delay to speed up the screenshot generator. There is no indication of any security vulnerability being fixed or introduced.
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.
* Added `fill_zero_fingerprints` and `_fill_zero_fingerprint_scope` to fill zero fingerprints each time before parsing a PSBT. * Modified `has_matching_input_fingerprint` to match also on zero fingerprint PSBTs and remove the (?) sign for matching seeds.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundaryseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Low 32/100
This commit changes how SeedSigner handles Bitcoin transaction files (PSBTs) that contain placeholder '00000000' fingerprints. Normally, a fingerprint identifies which wallet seed a transaction belongs to. Some wallet software exports incomplete data (xpub only, no derivation path), leaving zeros in the fingerprint field. Previously, SeedSigner could not recognize these transactions as belonging to the user's seed, showing a '?' and potentially refusing to sign. The new code tries to reconstruct the correct fingerprint by deriving public keys from the seed and comparing them. This is a usability fix, not a vulnerability patch, but it touches security-critical matching logic.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 18/100
This commit fixes a localization bug in a Bitcoin seed backup verification feature. It prevents BIP-39 seed words (which must stay in English) from being translated into other languages when displayed as quiz answers. Previously, translating these words could confuse users or make backup verification fail. There is no direct security exploit here, but it removes a usability/reliability issue in a security-sensitive workflow.
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This is a small internal cleanup change in a Bitcoin hardware wallet project. It replaces a manual flag used only during screenshot generation with an existing renderer property that already tells the code whether it is running in screenshot-generation mode. There is no user-facing or security-relevant change.
Refactor to enable auto-detection of screenshot generation renderer
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a small internal cleanup that changes how the screenshot test tool tells the splash screen to skip animations and delays. It replaces a parameter passed into the splash screen with a property checked on the renderer object. There is no security-relevant change for end users.
Merge pull request #782 from kdmukai/exclude_hw_drivers_from_coverage
[Testing] Exclude hardware drivers from `coverage`
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathsigning or wallet pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large merge that appears to be an initial repository import or branch synchronization for the SeedSigner project. It adds documentation, images, 3D enclosure files, CI workflows, Docker setup, and the full application source code. The commit title refers only to excluding hardware drivers from test coverage. There is no code change in the diff that fixes a security vulnerability, introduces a security feature, or alters cryptographic, wallet, or secret-handling logic.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large merge from the 'dev' branch into 'enable_persian'. The visible changes are almost entirely documentation, images, printable PDF templates, 3D enclosure files, GitHub workflow files, Docker setup, and project metadata. No source code changes that handle private keys, seeds, PSBTs, QR parsing, or cryptographic operations are visible in the supplied diff. There is nothing in the provided materials that indicates a security vulnerability.
Security candidateSentence case update for buttonsby FazleRabbbiferdaus172 · 53dc4817 · Sep 4, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · FazleRabbbiferdaus172
Sentence case update for buttons
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit only changes two button labels from title case to sentence case ("Discard Transaction" to "Discard transaction" and "Approve Transaction" to "Approve transaction"). It is a cosmetic text change with no security relevance.
Security candidatereplace PSBT text in codebase with Proposed transaction or Transactionby FazleRabbbiferdaus172 · 7df24a84 · Sep 3, 2025 · 4 filesMessage 65 · AdequateInformational 15Details
Commit message · FazleRabbbiferdaus172
replace PSBT text in codebase with Proposed transaction or Transaction
PSBT text replaced with Proposed Transaction
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundaryseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit only renames user-facing text strings. Every occurrence of 'PSBT' shown to the user is changed to 'Transaction' or 'Proposed Transaction' (for example, 'Review PSBT' becomes 'Review Transaction'). There are no code logic, security, or behavior changes.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a simple code cleanup (refactor) in the SeedSigner project. It removes an unused intermediate screen that asked users to choose a BIP-85 'application mode' and instead takes them directly to choosing 12 or 24 words. The actual behavior for users remains the same because only one application mode (BIP-39 child seed) was ever supported. There is no security issue here.
Security candidateMerge pull request #763 from kdmukai/exhaustive_psbtparser_testsby Nick Klockenga · fe7c671c · Aug 29, 2025 · 335 filesMessage 83 · StrongInformational 15Details
Commit message · Nick Klockenga
Merge pull request #763 from kdmukai/exhaustive_psbtparser_tests
[Test suite] Exhaustively test `PSBTParser` with all supported script types
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryseed or entropy pathsigning or wallet pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large merge of a test-only pull request titled 'exhaustive_psbtparser_tests'. The visible diff shows only new documentation, CI workflow, Docker, and project metadata files being added; no changes to the PSBTParser source code or runtime security logic are present in the supplied diff. It appears to be an initial repository population or a merge that brings in testing infrastructure and documentation rather than a security patch.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This is a minor code cleanup (DRY = Don't Repeat Yourself) in the user interface of a Bitcoin seed-signing device. It merges two nearly identical blocks of code that update the on-screen title into one shared block. There is no security-relevant change.
Security candidate[REF] logger in is moved above the commentby FazleRabbbiferdaus172 · 0d8e158e · Aug 27, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · FazleRabbbiferdaus172
[REF] logger in is moved above the comment
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit simply moves a log message one line earlier in the code, placing it above a comment instead of below it. There is no functional change, no security fix, and no behavior change. It is a minor code cleanup (refactoring).
Security candidate[REF] __post_init__ removed and RestartView initiates and start inside run methodby FazleRabbbiferdaus172 · 1334ad30 · Aug 27, 2025 · 1 fileMessage 50 · ThinInformational 12Details
Commit message · FazleRabbbiferdaus172
[REF] __post_init__ removed and RestartView initiates and start inside run method
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100
This is a small internal code cleanup in SeedSigner, a hardware wallet project. It moves the creation and starting of a background restart thread from a setup method into the main run method. There is no obvious security problem introduced by this change, and no security relevance is stated by the project.
Revert "explicit file regeneration check to screenshot generator"
This reverts commit e32604c1a60668079b207c0f00c9879ae5dfb651.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 12/100
This commit reverts a test-only change in the screenshot generator. The original change made the test delete any existing screenshot file before generating it, then verify a new file was actually created. The revert removes that explicit cleanup and verification. This is a testing/quality-of-life change, not a security fix or vulnerability introduction.
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.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This is a small cleanup change in a test screenshot generator script. It removes some leftover debug toast notifications and a custom exception used to exit a screenshot loop. There is no security relevance visible in the commit.
Add `ScreenshotRenderer` check to catch missing screenshots
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit adds a quality-check to the project's internal screenshot-generation test tool. It counts how many screenshots are produced and raises an error if a test view fails to render one. There is no change to the actual SeedSigner wallet application or its security.
explicit file regeneration check to screenshot generator
Previously, there were no checks to determine if a file was correctly generated by the generator. It was even hard to detect because of previously generated files.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI analysis · Informational 13/100
This change improves a test helper that creates screenshots for documentation. It now deletes any old screenshot before generating a new one and throws an error if the new file is not created. This is a quality improvement for tests, not a security fix for user-facing code.
Security candidatelog moved to DoResetThreadby FazleRabbbiferdaus172 · 674945e9 · Aug 25, 2025 · 1 fileMessage 58 · ThinInformational 13Details
Commit message · FazleRabbbiferdaus172
log moved to DoResetThread
Placing the log message inside the thread means it gets written at the exact moment the restart process actually begins. As in case of restart view this never gets executed. Better encapsulates the component responsible for rest.
This commit simply moves a log message that says 'Restarting SeedSigner' from one place in the code to another place inside the restart thread. It does not change what the program does, only when a status message is recorded. There is no security issue visible in this change.
run_screen need to be executed by screenshot generator test to generate png for restart view. But we don't want to restart so the not starting the thread should be the way.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit fixes a screenshot-generation test issue. Previously, the RestartView skipped rendering entirely when used by the screenshot generator, so no PNG image was produced for the restart screen. The change now renders the reset screen but only starts the actual restart thread when not in screenshot mode. There is no security issue here.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundaryseed or entropy pathsigning or wallet pathauthentication pathparser or protocol path
AI analysis · Informational 15/100
This commit is a massive initial repository import or merge of the entire SeedSigner project into the branch. It adds documentation, images, 3D enclosure files, GitHub workflows, Docker files, and source code. The commit title mentions only one file (psbt_screens.py), but the actual diff covers 328 files and is almost entirely additive. There is no evidence in the supplied materials of any security vulnerability, malicious change, or code defect.
Security candidaterefactor: replace `.display()` with `View.run_screen`by okaybro · 80af82aa · Aug 15, 2025 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · okaybro
refactor: replace `.display()` with `View.run_screen`
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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a straightforward internal code cleanup: it replaces direct calls to a screen's `.display()` method with a new helper called `self.run_screen()`. The user-visible behavior appears unchanged; it is a refactoring, not a security fix.
Security candidatefeat: highlight high fees in PSBTOverview and PSBTMath Screenby okaybro · 5b15804a · Aug 14, 2025 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · okaybro
feat: highlight high fees in PSBTOverview and PSBTMath Screen
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing boundaryseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit adds a visual warning (a red "(!)") next to the fee label when a Bitcoin transaction has unusually high fees. It is a user-interface safety improvement, not a fix for a software vulnerability. There is no change to how transactions are validated, signed, or rejected.