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.
Lower-priorityExplicit description template; minor presentation reformatting; docs link fixby kdmukai · aa4e3293 · Feb 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · kdmukai
Explicit description template; minor presentation reformatting; docs link fix
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 analysis · Informational 15/100
This commit only updates the GitHub pull request template. It restructures the description section, adds prompts for screenshots, fixes one documentation link, and reformats checklists. No application code, tests, build scripts, or security-sensitive files were changed.
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.
Lower-priorityAdd `mock_context_manager`; factor out all `run_before` methodsby kdmukai · b609abb6 · Jan 20, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · kdmukai
Add `mock_context_manager`; factor out all `run_before` methods
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit is a test-code cleanup only. It replaces manual 'before/after' setup callbacks in the screenshot generator with reusable Python context managers that automatically clean up mock data. There is no change to the actual SeedSigner application or its security behavior.
✓ 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 tiny code cleanup commit in a single display driver file. It adds the Python dataclass decorator to a class and renames one method parameter from 'state' to 'enabled' to match the rest of the code. There is no visible security relevance.
Security candidateRename to `BaseDisplayDriver`; ili9341 changesby kdmukai · 777f6041 · Jan 20, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai
Rename to `BaseDisplayDriver`; ili9341 changes
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 is a routine internal code cleanup. It renames the parent display class from DisplayDriver to BaseDisplayDriver, makes a couple of methods optional instead of requiring every display subclass to implement them, and adjusts the ILI9341 display driver to inherit from the new base class. There is no visible security fix or vulnerability being addressed.
Security candidateRefactor `DisplayDriver` to be a true parent class; add Factoryby kdmukai · 6fed5e88 · Jan 20, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · kdmukai
Refactor `DisplayDriver` to be a true parent class; add Factory
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 routine internal code reorganization. It restructures how the SeedSigner app creates and manages its screen drivers, turning the existing display controller into a parent class and adding a factory pattern. There is no indication this change fixes a security bug or introduces a security vulnerability.
✓ 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 · Low 35/100
This commit hardens how SeedSigner loads multiselect settings from saved files or QR codes. Previously, an empty or malformed multiselect value (for example, an empty string, a lone comma, or a missing entry) could leave the setting empty, which might cause unexpected behavior when the app later uses that setting. The patch now strips empty pieces from comma-separated input and falls back to the default value whenever the result is empty. A new test checks four empty/missing cases.
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.
✓ 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 · Low 31/100
This commit fixes a bug in how SeedSigner reloads saved settings. If a setting that is supposed to be a list of choices (a 'multiselect') was saved as empty/None, the app could behave incorrectly. The patch makes the app fall back to the default list instead. It is a defensive fix rather than a clear-cut remote exploit.
Security candidateSettingsQR values cannot be blankby kdmukai · adaf3d1f · Jan 20, 2026 · 2 filesMessage 45 · ThinLow 36Details
Commit message · kdmukai
SettingsQR values cannot be blank
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 · Low 36/100
This commit fixes a bug in how SeedSigner reads setup information from a QR code. Previously, if a setting value was left blank (for example, 'sigs=' with nothing after the equals sign), the app would silently accept it and could misinterpret later settings. Now the app rejects blank values and reports an error. This is a defensive hardening change rather than a confirmed exploit, but it prevents potential misconfiguration or unexpected behavior.
Security candidateUX changes to require a selection for multiselect settingsby kdmukai · 6e25e3f9 · Jan 20, 2026 · 3 filesMessage 50 · ThinInformational 23Details
Commit message · kdmukai
UX changes to require a selection for multiselect settings
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 23/100
This commit adds a user-experience guard so that settings where multiple options can be toggled now require at least one option to remain selected. Previously, a user could back out of such a setting with nothing selected, which could leave the device in an unintended or non-functional configuration. The fix shows a warning and returns the user to the setting until they pick at least one option.
Lower-priorityRemove duplicated attr entry in testby kdmukai · 3f9ec5c3 · Dec 28, 2025 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · kdmukai
Remove duplicated attr entry in test
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100
This commit removes a duplicate setting in a single test string. It is a minor test cleanup with 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.
Lower-priorityrefactor screenshot generator after `mock_context_manager` mergeby kdmukai · 1d433b10 · Dec 27, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · kdmukai
refactor screenshot generator after `mock_context_manager` merge
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit only changes a test helper script that generates screenshots for documentation. It adds a mock that makes the screenshot generator pretend the software is running the latest released version instead of the current development code. There is no change to the actual SeedSigner application or its security behavior.
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.
Lower-priorityAdd `mock_context_manager`; factor out all `run_before` methodsby kdmukai · 037756da · Dec 27, 2025 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · kdmukai
Add `mock_context_manager`; factor out all `run_before` methods
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit is a test-only code cleanup. It replaces manual before/after setup callbacks with reusable Python context managers in the screenshot generator test harness. There is no change to the actual SeedSigner application code that users run, so it cannot affect real wallets, transactions, or security.
Security candidateAdd `is_release_image` and related testby kdmukai · 797d036a · Dec 27, 2025 · 3 filesMessage 55 · ThinInformational 15Details
Commit message · kdmukai
Add `is_release_image` and related test
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit adds a helper function that decides whether the running software is an official release image. It then uses that helper to hide extra technical details (fork name and commit hash) from the version screen only for official releases. There is no security fix or vulnerability here; it is a UI refinement with tests.
Adds Github Actions CI `SOURCE_SHA` custom env var
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 routine improvement to how SeedSigner reads version information during automated GitHub testing. It adds a new environment variable SOURCE_SHA so that when outside contributors open pull requests, the displayed commit hash points to the contributor's actual latest commit rather than a temporary merge commit GitHub creates internally. There is no security vulnerability here.
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.
Security candidateGithub Actions CI env var improvementsby kdmukai · e08442dd · Dec 26, 2025 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai
Github Actions CI env var improvements
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 improves how the SeedSigner software detects its own version information when running automated tests in GitHub Actions. It adds new environment variables so that pull request builds correctly show the contributor's branch name and username instead of misleading placeholder values. There is no security vulnerability here; it is a quality-of-life improvement for build metadata.
Security candidateGithub Actions CI timestamp format bugfixby kdmukai · 3394d0cb · Dec 26, 2025 · 2 filesMessage 45 · ThinInformational 19Details
Commit message · kdmukai
Github Actions CI timestamp format bugfix
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 19/100
This commit fixes a small date-parsing bug in the software's version helper. When the code runs in GitHub Actions, Git reports the latest commit time ending in 'Z' (a common UTC notation), but the Python function used to read that date didn't understand 'Z' before Python 3.11. The patch simply replaces 'Z' with '+00:00' so the date parses correctly. It is a compatibility fix, not a security fix.