SS
← All projectsSeedSigner

SeedSigner

Stateless, air-gapped Bitcoin signing software for Raspberry Pi hardware.

BitcoinHardware walletsNormal
Repository coverage

285 commits in the local evidence base

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.

214security candidates37second-pass queue278AI analyses
14commits · 30 days
52commits · 60 days
111commits · 180 days
230commits · 365 days
Backfill bands
Aug 5 → Feb 6150 seen8 candidatesComplete
Feb 6 → Jun 629 seen0 candidatesComplete
Jun 6 → Jul 60 seen0 candidatesComplete
Jul 6 → Aug 57 seen1 candidatesComplete
Commit communication

Does the history explain itself?

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
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nick Klockenga413337769
kdmukai158114158348
okaybro282427068
newtonick181317049
PROWLERx15101010020
alvroble12711055
FazleRabbbiferdaus172868061
biel414037
SeedSigner111058
Chaitanya-Keyal111057
Kshitij111033
S1DDHEY111045
Analysis record

Published AI watches

Last scanned 18 minutes ago

High 80 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1073 from kdmukai/2026-10_psbt_change_path_rules

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
5f321768by Nick Klockenga+1863−1397 files
Vendor flagged security relevance
High 81 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1060 from kdmukai/2026-10_psbt_input_claims

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
995ce5c6by Nick Klockenga+990−1406 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Reword the input claim checks' docstrings

This commit only rewrites comments and documentation strings in code and tests. No program logic, behavior, or security checks were changed.

081b1f40by kdmukai+13−155 files
No security note in commit
Moderate 69 AI analysisMessage 95 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Refuse mixed base paths on single sig segwit v0

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
9130ac75by kdmukai+432−875 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Measure the change window from the smallest input index

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)
512329beby kdmukai+57−102 files
Vendor flagged security relevance
Informational 12 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Test change at an extra level under the base path

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
9c19e9d6by kdmukai+17−31 file
No security note in commit
High 81 AI analysisMessage 85 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Check change derivation paths against the inputs

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
862ed41bby kdmukai+1285−507 files
Vendor flagged security relevance
Informational 14 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Show the psbt's warnings through one View

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
a8602100by kdmukai+163−784 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Add a test helper to set an input's locking script

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.

b297c869by kdmukai+31−553 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Document held findings at the steps that hold them

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…

1ba3c6a1by kdmukai+37−232 files
No security note in commit
High 78 AI analysisMessage 88 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1047 from kdmukai/2026_09_psbt_input_scripts

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
ada81cdeby Nick Klockenga+598−795 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 18 · Opaque
SS SeedSignerSeedSigner BitcoinHardware wallets

Enable Swahili

This commit simply adds Swahili as a new language option in the SeedSigner settings. It is a routine localization change with no security relevance.

c255bf57by kdmukai+2−01 file
No security note in commit
Moderate 51 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1042 from Chaitanya-Keyal/op-return-push-opcode

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
d8f7956fby Nick Klockenga+375−156 files
No security note in commit
Moderate 64 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1041 from Chaitanya-Keyal/psbt-negative-fee

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)
ebc1e11fby Nick Klockenga+105−65 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Drop the negative fee comment's claim that both totals are unverified

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…

9994a04eby okaybro+3−41 file
No security note in commit
High 81 AI analysisMessage 88 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #995 from newtonick/psbt-verify

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
e92c4ea6by Nick Klockenga+508−346 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Trim the input-amount verification test docstrings

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.

afb7305aby newtonick+17−261 file
No security note in commit
Informational 12 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Tighten the input-amount test asserts and run the no-utxo test over every fixture

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…

222bf3d5by newtonick+12−91 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Replace the parse() test helper with direct PSBTParser calls

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…

a71b7b39by newtonick+11−131 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateSimplify SeedSigner OS builder pathby kdmukai · d2914c33 · Dec 26, 2025 · 4 filesMessage 45 · ThinInformational 20Details
Commit message · kdmukai

Simplify SeedSigner OS builder path

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 20/100

This commit refactors how SeedSigner determines and records its software version. It removes an environment-variable-based build path and instead reads version info directly from git. The change is mostly cleanup and testing improvements. There is no obvious security vulnerability, but the code still uses shell commands (os.popen) and parses git output, which can be risky if inputs are ever attacker-controlled. Here, the inputs come from the local git state or trusted environment variables, so the practical risk is low.

Security candidateRemove unnecessary error messageby kdmukai · 9d6a93b9 · Dec 26, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · kdmukai

Remove unnecessary error message

35/100 · OpaqueMessage clarity
✓ 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 commit simplifies a custom camera error exception by removing a hard-coded user-facing error message. The exception still exists and will still be raised; it just no longer automatically includes the text 'Camera error. Check camera connections.' There is no security-relevant change visible in the diff.

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.

Lower-prioritySimplify version.json file write; standardize on matching SeedSigner OS builder output even in local devby kdmukai · 7b5d21f6 · Dec 25, 2025 · 1 fileMessage 50 · ThinInformational 12Details
Commit message · kdmukai

Simplify version.json file write; standardize on matching SeedSigner OS builder output even in local dev

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 12/100

This commit refactors a small developer utility that writes a version.json file. It changes how the script decides whether it is running in the official build environment versus a local development copy, and makes the generated version file match the official build format even when built locally. There is no obvious security problem in the diff itself.

Security candidateNaming clean up; version.json gets "v" prefix; explicit SeedSigner OS builder pathsby kdmukai · 0a02616c · Dec 25, 2025 · 5 filesMessage 50 · ThinInformational 15Details
Commit message · kdmukai

Naming clean up; version.json gets "v" prefix; explicit SeedSigner OS builder paths

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 code cleanup and build-system improvement. It renames internal variables (for example, changing 'version_commit_hash' to 'short_commit_hash'), makes the version string consistently include a 'v' prefix, and adds explicit support for detecting the SeedSigner OS build environment. There is no change that affects security or user safety.

Security candidatere-org section placement; minor test name fixups after renamesby kdmukai · 6cd932ab · Dec 25, 2025 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · kdmukai

re-org section placement; minor test name fixups after renames

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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply moves a block of existing code (the git shell command helpers) to a different location in the same file and renames a couple of test methods. No behavior changes, no security fixes, and no new vulnerabilities are introduced.

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.

Security candidateSlight test case reorg; additional tests to maintain 100% coverageby kdmukai · 65009775 · Dec 25, 2025 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · kdmukai

Slight test case reorg; additional tests to maintain 100% coverage

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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is purely a code cleanup and test expansion. It renames internal helper methods in the version utility to be clearer (for example, changing `_get_version_name_from_env_var` to `_get_version_name_from_seedsigner_os_env_var`), reorganizes comments, and adds new tests to keep test coverage at 100%. There is no change to user-facing behavior, no fix for a bug, and no security-related change.

Lower-priorityGet coverage back to 100%by kdmukai · 38c55847 · Dec 25, 2025 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · kdmukai

Get coverage back to 100%

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 only adds a new unit test to the project's test suite. It verifies that a version-reporting override method works correctly and that the override is blocked when running on the actual SeedSigner OS. There are no changes to production code, no bug fixes, and no security-related behavior changes.

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.

Security candidaterestore Version.override_data for screenshot generatorby kdmukai · 10767de9 · Dec 24, 2025 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · kdmukai

restore Version.override_data for screenshot generator

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 18/100

This commit restores a helper function that lets the project’s screenshot generator temporarily override version information shown in screenshots. The function is decorated so it cannot run on the actual SeedSigner OS device. It only affects display text used in documentation screenshots, not private keys, seeds, or transaction logic.

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.

Security candidateInterim commit; coverage at 100%by kdmukai · 74ebe10b · Dec 24, 2025 · 3 filesMessage 55 · ThinInformational 14Details
Commit message · kdmukai

Interim commit; coverage at 100%

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 14/100

This commit is a routine internal refactor of how the app reads its own version information (version name, fork, timestamp, commit hash). It consolidates singleton setup, renames constants and methods, adds GitHub Actions CI detection, and expands unit tests to reach 100% code coverage. There is no direct evidence in the commit that this fixes a security vulnerability or introduces a new attack path. The changes are mostly about making version reporting more reliable and testable.

Security candidateAdding tests, bugfixes; interim commitby kdmukai · c5efda30 · Dec 23, 2025 · 4 filesMessage 55 · ThinInformational 15Details
Commit message · kdmukai

Adding tests, bugfixes; interim commit

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 is mostly a routine code cleanup and test expansion for how SeedSigner reports its software version. It renames a decorator, adds more tests, improves error handling when files are missing, and fixes a timestamp formatting bug when checking GitHub releases. There is no direct evidence in the commit that this fixes an active security vulnerability, but it does reduce risky behavior such as silently swallowing errors and making unverified shell calls in some contexts.

Security candidateHuge refactor; interim commitby kdmukai · 47212c98 · Dec 22, 2025 · 7 filesMessage 35 · OpaqueInformational 16Details
Commit message · kdmukai

Huge refactor; interim commit

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 16/100

This is a large code refactor that changes how SeedSigner detects and displays its software version. It replaces a simple version reader with a more complex singleton system that reads git state, environment variables, and a JSON file. The changes are mostly about version reporting and do not appear to alter how private keys, seeds, or Bitcoin transactions are handled. There is no clear security bug visible in the diff, but the refactor introduces new code paths that touch files and shell commands, which always carry some risk of mistakes.

Security candidatebugfixby kdmukai · 272db5df · Dec 20, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · kdmukai

bugfix

0/100 · OpaqueMessage clarity
! Very short subject! 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 commit fixes a bug in how SeedSigner determines and reports its software version. Previously, the version was set once and could be left blank or stale in certain build situations. The patch makes version detection more reliable by trying multiple sources: an environment variable, the current Git branch, the latest Git tag, and finally the short commit hash. There is no direct evidence this is a security fix, but reliable version reporting helps users and developers confirm they are running the expected software.

Lower-priorityAdd version.json to .gitignoreby kdmukai · 516a76ba · Dec 20, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Add version.json to .gitignore

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply adds one file path to the project's .gitignore list, telling Git not to track a generated version.json file. There is no code change, no security fix, and no vulnerability introduced.

Security candidatedebuggingby kdmukai · 906f21cc · Dec 20, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · kdmukai

debugging

0/100 · OpaqueMessage clarity
! Very short subject! 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 commit adds a single debug print statement that displays the value of an environment variable used during the build process. It does not change how the software works, does not introduce a security flaw, and does not affect end-user security. It is a routine development/debugging change.

Security candidateTry to pull version name from CI env varsby kdmukai · 97386fff · Dec 20, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Try to pull version name from CI env vars

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 changes how the SeedSigner software figures out its own version number when it cannot read version info from the local git repository. Instead of immediately giving up, it now checks whether it is running inside GitHub Actions and, if so, uses environment variables provided by GitHub to determine the version. There is no security issue visible in this change.

Security candidateUse `git` directly to get branch or tag nameby kdmukai · d02e9805 · Dec 20, 2025 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · kdmukai

Use `git` directly to get branch or tag name

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 18/100

This commit removes a leftover debug print statement and changes how the software figures out its own version name by asking the Git tool directly instead of relying on a pre-existing file. The change itself is not a security fix, but it removes a minor information leak (the hostname) and avoids a build-time dependency on a generated file. There is no evidence this was reported as a security issue or credited to a researcher.

Security candidaterename and bugfixby kdmukai · 657167ac · Dec 20, 2025 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

rename and bugfix

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 commit simply renames a method from get_last_edit to get_last_edit_timestamp and updates the places that call it and test it. There is no security issue here—just a cleanup to fix a naming mismatch (the caller was already using a name that did not exist).

Security candidateUse `git log` for most recent commit's edit time when writing version.jsonby kdmukai · 3f7803fa · Dec 20, 2025 · 1 fileMessage 50 · ThinInformational 14Details
Commit message · kdmukai

Use `git log` for most recent commit's edit time when writing version.json

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 14/100

This commit changes how SeedSigner records the 'last edit time' in its version.json file. Previously it scanned all source files for the most recent modification time. Now it runs a git command to use the most recent commit timestamp. The main concern is that it uses os.popen(), which executes a shell command, and does not validate the output. In normal use this is benign, but if an attacker can control the working directory or git executable, it could become a command-injection or misleading-metadata issue. There is no direct evidence this is being exploited.

Security candidateUse SeedSigner OS env var; enforce utc timeby kdmukai · 37531c03 · Dec 20, 2025 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · kdmukai

Use SeedSigner OS env var; enforce utc time

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 changes how SeedSigner records its software version and build timestamp. It now reads a version name from an environment variable used by SeedSigner OS and forces the last-edit timestamp to UTC. These are build-process improvements, not fixes for an active security vulnerability. The only security-relevant aspect is a small hardening of how external shell commands and environment input are handled.