FD
← All projectsFoundation

Passport firmware

Firmware for Foundation Passport Bitcoin signing devices.

BitcoinHardware walletsNormal
Repository coverage

263 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.

102security candidates79second-pass queue215AI analyses
42commits · 30 days
128commits · 60 days
194commits · 180 days
256commits · 365 days
Backfill bands
Aug 5 → Feb 612 seen0 candidatesComplete
Feb 6 → Jun 659 seen3 candidatesComplete
Jun 6 → Jul 64 seen0 candidatesComplete
Jul 6 → Aug 52 seen0 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.

61/100 average clarity
16Strong · 80–100
116Adequate · 60–79
118Thin · 40–59
13Opaque · 0–39
4security 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.
Jacksper13321424466
Matt Gleason841868351
Jack603454261
mjg-foundation693251269
Jean-Pierre De Jesus DIAZ828061
Ken Carpenter313048
QnA111060
dependabot[bot]505076
BitcoinQnA101045
Analysis record

Published AI watches

Last scanned 19 minutes ago

Informational 12 AI analysisMessage 78 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8696: remove the Security Check from onboarding

This commit removes the 'Security Check' step from the initial device setup (onboarding) for the Passport hardware wallet. To avoid breaking devices that were mid-setup during a firmware update, the old step is kept as a harmless pass-thro…

8d77ba38by Jack+153−124 files
No security note in commit
Low 37 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #753 from Foundation-Devices/sft-8680-fail-to-sign-dynamic-taproot-qr-message

This commit adds support for signing BIP-322 message requests that wallets like Sparrow send as a PSBT (a Bitcoin transaction-like data format). It is a feature addition, not a reported vulnerability fix. The code includes careful validati…

New input parser for externally supplied PSBT data with explicit structural validationRejects non-Taproot BIP-322 requests and unsafe sighash typesBinds the user-reviewed message and address to the transaction being signed
5e98b6abby mjg-foundation+722−3011 files
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8680: check derivation path length before indexing into it

This commit fixes a bug in the Passport hardware wallet's BIP-322 message signing code. Previously, when parsing a PSBT (a Bitcoin data format), the code could read past the end of an empty or too-short 'derivation path' field because it c…

Out-of-bounds read / index error on untrusted PSBT inputValidation order bug: first-byte check before length checkBIP-322 signing request parsing hardened
cec3925bby Matt Gleason+8−43 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #754 from Foundation-Devices/sft-8681-passport-core-sign-taproot-messages-with

This commit changes how the Passport hardware wallet signs Bitcoin Taproot text messages. Previously it used SIGHASH_DEFAULT (the Taproot default), but now it uses SIGHASH_ALL. The change is for compatibility: the commit message says Sparr…

Change in cryptographic signature hash type (SIGHASH_DEFAULT -> SIGHASH_ALL)Comment explicitly references verifier compatibility and Sparrow wallet acceptanceUnit test asserts new signature encoding and verifies against an external test vector
87f43de1by mjg-foundation+22−172 files
No security note in commit
Low 41 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #752 from Foundation-Devices/sft-8674-passport-core-signing-flow-does-not-show-a-non

This commit adds on-screen warnings to the Passport hardware wallet when a user is reviewing a Bitcoin transaction that contains timelocks. Timelocks can prevent a transaction from confirming until a future date or until certain inputs hav…

UI warning for absolute time-based nLockTimeUI warning for BIP68 relative timelocks on version-2 transactionsHeight-based nLockTime intentionally not flagged to avoid false positives
5defe2c5by mjg-foundation+176−16 files
No security note in commit
Moderate 52 AI analysisMessage 85 · Strong
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8674: warned about timelocks when reviewing a transaction

This commit adds on-screen warnings to the Passport hardware wallet when a Bitcoin transaction being reviewed includes a timelock that could delay confirmation. Before this change, a user could unknowingly sign a transaction that is blocke…

UI now warns users about transaction timelocks that delay confirmationPreviously undisclosed to the signer: absolute date locks and BIP68 relative locksHeight-based nLockTime intentionally not flagged to avoid warning fatigue
7cba5349by Jack+176−16 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #747 from Foundation-Devices/sft-8653-passport-core-recheck-the-firmware-image-while

This update tightens the firmware update process on the Passport hardware wallet. Previously, the device verified the firmware file once, then copied it to internal flash memory without re-checking. A malicious or tampered file swapped in …

Time-of-check/time-of-use (TOCTOU) hardening in firmware update pathNew digest parameter threaded from verification task to staging taskStaging task now re-hashes firmware image and compares against expected digest
3449381fby mjg-foundation+68−264 files
No security note in commit
Moderate 60 AI analysisMessage 58 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #736 from Foundation-Devices/sft-8554-bootloader-setup-checks

This commit hardens how Passport's bootloader handles a sensitive factory key during initial device setup. Previously, the code trusted that erasing the key from SPI flash succeeded without checking, and it left a temporary copy of the key…

Sensitive key material (supply-chain validation key) is now explicitly zeroed from stack memory after useSPI flash erase of the SCV key is now verified by read-back instead of assumed successfulBootloader setup now aborts if the SCV key cannot be confirmed erased from SPI flash
ed62d448by mjg-foundation+245−55 files
No security note in commit
Moderate 62 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #735 from Foundation-Devices/sft-8555-update-restore-checks

This commit adds security checks when restoring a backup file to a Passport hardware wallet. Previously, multisig wallet configurations stored in a backup were restored without verifying that they actually belong to the seed being restored…

Validation of multisig backup records against restored seedDerivation verification for xpubs claiming backup root fingerprintDropping malformed records instead of failing entire restore
8dbae7e1by mjg-foundation+242−75 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #748 from Foundation-Devices/sft-8654-passport-core-bounded-text-building-in-the

This commit replaces unsafe string-copying functions in the Passport hardware wallet's bootloader with a bounded helper that prevents text fields from overflowing their buffers. The change is defensive: it stops malicious or malformed firm…

Replacement of strcpy/strcat with bounded append_text helperHandling of non-NUL-terminated firmware header text fieldsBuffer overflow mitigation in bootloader UI message construction
e2d735f0by mjg-foundation+89−222 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #732 from Foundation-Devices/sft-8545-native-taproot-key-signing

This commit adds a new, dedicated way for the Passport hardware wallet to sign Bitcoin Taproot transactions. It moves the cryptographic 'tweak' calculation from Python code into a Rust library and adds unit tests. There is nothing in the c…

5e3ed701by mjg-foundation+234−185 files
No security note in commit
Moderate 60 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #742 from Foundation-Devices/sft-8530-distinct-cosigners

This update to the Passport hardware wallet firmware adds a safety check when importing multi-signature wallet configurations. Previously, the same cosigner public key could be listed more than once under different fingerprints or address …

Adds duplicate-key detection during multisig wallet importCompares raw public-key x-coordinates rather than fingerprints or encoded xpub stringsPrevents a single key from being counted as multiple independent cosigners
92c68c63by mjg-foundation+69−03 files
Vendor flagged security relevance
Low 48 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #739 from Foundation-Devices/sft-8559-psbt-file-errors

This update fixes a bug where the Passport hardware wallet could freeze (hang) when reading a malformed or unreadable PSBT transaction file from a microSD card. Now the device reports a clear error instead of getting stuck, so users know s…

Denial-of-service / UI hang on malformed input now returns an errorUnhandled exception path now caught and reported instead of leaving task unresolvedMissing microSD card case explicitly reported
6a461136by mjg-foundation+144−62 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #740 from Foundation-Devices/sft-4482-update-card-missing

This commit fixes a user-experience bug in the Passport hardware wallet's firmware update flow. Previously, if the user removed the microSD card while the device was reading a firmware update file, the process would crash with an unhandled…

Adds exception handling for a removable-media failure during a privileged operation (firmware update)Prevents unhandled CardMissingError from aborting the update flow abruptlyDoes not alter firmware signature, timestamp, or header validation logic
06ec8d6aby mjg-foundation+109−23 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #741 from Foundation-Devices/sft-737-multisig-match-n

This firmware update fixes a bug in how the Passport hardware wallet matches multisignature (multisig) wallets. Previously, when looking for a saved wallet that matches the cosigners in a transaction, the device only checked that the cosig…

Incorrect multisig wallet matching could lead to signing with the wrong wallet policySubset-only cosigner matching allowed a smaller wallet to be conflated with a larger oneFix adds N filter to wallet candidate enumeration
d2d30a58by mjg-foundation+59−23 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #746 from Foundation-Devices/sft-8260-evaluate-miniscript-no-compatible-path

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction's timelock conditions are not yet met. It does not change any security logic, validation, or behavior. The old message said no s…

f6ab63ceby Jacksper13+5−42 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8260: Update the policy no-compatible-path warning copy

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction cannot be signed because no spending path's time-lock conditions are currently satisfied. It does not change any security logic,…

e024471eby Jack+5−42 files
No security note in commit
Informational 21 AI analysisMessage 58 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #731 from Foundation-Devices/SFT-974-miniscript-ui-followup

This commit is a follow-up to the miniscript wallet-policy user interface. It mostly fixes UI wording, memory cleanup, and policy display logic. The only potentially security-relevant change is that wallet policy IDs are now computed with …

Incremental SHA-256 digest used for policy ID computationRemoval of explicit `validate(miniscript, context)` call before compilationNew default-name derivation from descriptor checksum
83d1d576by mjg-foundation+415−5312 files
No security note in commit
Low 32 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-974: unwrapped miniscript parsing recursion, added default policy

This firmware update changes how the Passport hardware wallet handles complex Bitcoin wallet policies. The main visible change is replacing a recursive parser walk with an iterative one, which prevents the device from crashing due to exces…

Recursion in miniscript parsing replaced with explicit stack to avoid RecursionError on deeply nested templatesPolicy validation path changed: explicit `validate()` call removed, safety now enforced via `compile_miniscript()` during registrationDefault empty policy name now auto-populated from descriptor checksum to avoid unnamed policies
96b2aa9fby Matt Gleason+160−216 files
No security note in commit
Informational 20 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-974: improved miniscript UI, working on OOM issues

This commit is a routine feature and stability patch for the Passport hardware wallet's miniscript wallet-policy support. It improves on-screen descriptions of wallet policies, adds explicit memory cleanup (garbage collection) during polic…

Memory pressure mitigation via explicit garbage collection during policy operationsNew verify-address flow for registered wallet policiesUI clarity improvements for timelock and signer-role descriptions
cb7478a5by Matt Gleason+255−3210 files
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.

Lower-priorityBound microSD message read at read time, not via separate statby Jack · c8f53cf8 · May 13, 2026 · 1 fileMessage 73 · AdequateModerate 59Details
Commit message · Jack

Bound microSD message read at read time, not via separate stat

A separate stat in its own CardSlot() left a TOCTOU window where a swapped file could still be read unbounded. Move the cap into a bounded read_fn inside the read.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Moderate 59/100

This commit fixes a security bug in the Passport hardware wallet's microSD message-signing flow. Previously, the firmware checked a file's size in one operation and then read it in another. Because the microSD card could be swapped between those two moments, a malicious file larger than the allowed limit could still be loaded. The fix reads only a bounded number of bytes in a single operation, closing that window.

Lower-prioritySFT-6948: fixed add-secrets portability, removed unnecessary error wallingby Matt Gleason · 7a55a01e · May 12, 2026 · 2 filesMessage 65 · AdequateInformational 18Details
Commit message · Matt Gleason

SFT-6948: fixed add-secrets portability, removed unnecessary error
walling

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 18/100

This is a small build-tool fix in the factory/secrets-injection utility used during Passport device manufacturing. It replaces a non-portable type name (`ulong`) with the standard C type (`unsigned long`) and removes a compiler flag that was suppressing the resulting error. There is no direct evidence this change fixes an exploitable security vulnerability; it appears to be a portability/correctness cleanup that lets the tool compile cleanly across build environments.

Security candidateEnforce MSG_SIGNING_MAX_LENGTH on microSD message signingby Jack · a6dfc59f · May 11, 2026 · 1 fileMessage 81 · StrongModerate 63Details
Commit message · Jack

Enforce MSG_SIGNING_MAX_LENGTH on microSD message signing

Restores the file-size cap that the deleted SignTextFileFlow used to
provide before its consolidation in #636. Gated on normal_signing so
health-check files (with their own implicit length constraints) are
unaffected.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundary
AI analysis · Moderate 63/100

This commit fixes a missing safety limit in the Passport hardware wallet's microSD message-signing feature. Previously, a user could accidentally or maliciously be asked to sign an extremely large file from the microSD card, which could strain memory, cause crashes, or be used in a denial-of-service-style attack. The change restores a maximum file-size check that existed in older code but was lost when two code paths were merged. Health-check files are exempt because they already have their own built-in size limits.

Security candidatePass expected_address through QR message signing pathby Jack · 80fda3a1 · May 11, 2026 · 1 fileMessage 81 · StrongModerate 59Details
Commit message · Jack

Pass expected_address through QR message signing path

Mirrors the WYSIWYG-signing assertion that microSD signing already has
(added in #636). Keeps self.address raw (used as expected_address) and
uses a local display_address for stylization in the preview.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 59/100

This commit fixes a consistency issue in the QR-code message-signing flow of the Passport hardware wallet. Previously, when signing a message via QR code, the wallet did not pass the user-confirmed address down to the signing code as an explicit 'expected address' check. The microSD signing path already had this safety check. After the change, the raw, verified address is passed through and used to confirm the signature is for the correct address, while a stylized version is still shown on screen. This reduces the risk that a tricked or confused user signs a message with the wrong address.

Security candidateSFT-3834: fixed return type for quitting message signingby Matt Gleason · 3f29f056 · May 11, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Matt Gleason

SFT-3834: fixed return type for quitting message signing

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 19/100

This commit fixes a minor return-value bug in the Passport hardware wallet's health-check flow. When the user cancels message signing, the flow now returns 'None' instead of 'False'. This is a correctness fix that likely prevents a downstream caller from misinterpreting a user cancellation as a failed health check. There is no direct evidence in the commit that this is exploitable for theft, bypass, or denial of service.

Lower-prioritySFT-3834: formatted code, added autopep8 to nix devshellby Matt Gleason · e77f08d3 · May 9, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-3834: formatted code, added autopep8 to nix devshell

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 purely cosmetic: it reformats Python code to follow style rules, fixes spacing around '@classmethod' decorators, and adds an auto-formatting tool (autopep8) to the developer environment. No program behavior or security properties change.

AI review queuedSFT-3834: ensured preview address matches the signed output addressby Matt Gleason · 434d4bcc · May 9, 2026 · 3 filesMessage 50 · ThinModerate 59Details
Commit message · Matt Gleason

SFT-3834: ensured preview address matches the signed output address

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This firmware update fixes a bug where the Bitcoin address shown on the Passport hardware wallet screen before signing could differ from the address actually used to create the signature. The fix makes the signing task verify that the address it computes matches the address previewed to the user, and aborts if they don't match. This prevents a user from being tricked into approving a signature for one address while the device signs with another.

AI review queuedSFT-3834: removed unused security_menu and sign_text_file_flowby Matt Gleason · d7a7b23d · May 8, 2026 · 4 filesMessage 50 · ThinInformational 12Details
Commit message · Matt Gleason

SFT-3834: removed unused security_menu and sign_text_file_flow

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit simply removes an unused feature that let users sign a text file from a microSD card. There is no indication of a security bug being fixed; it appears to be dead-code cleanup.

Lower-prioritySFT-6948: removed unnecessary add-secrets build inputs and inherited itemsby Matt Gleason · 9c1e3654 · May 8, 2026 · 2 filesMessage 65 · AdequateInformational 11Details
Commit message · Matt Gleason

SFT-6948: removed unnecessary add-secrets build inputs and inherited
items

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 11/100

This commit removes unused build dependencies from a Nix build script that adds secrets to Passport firmware. The change drops references to pkg-config and OpenSSL that were apparently not actually needed. There is no direct evidence this fixes a security vulnerability; it appears to be a cleanup or build-hardening change.

Lower-prioritySFT-6948: added "add-secrets" to devshellby Matt Gleason · f4f7b4ca · May 6, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6948: added "add-secrets" to devshell

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

This commit adds a developer-only build helper called 'add-secrets' to the project's Nix development shell. It does not change the firmware that runs on user devices, nor does it alter how secrets are generated, stored, or protected in production. It simply makes an existing internal tool easier for developers to compile and run during build/test workflows.

AI review queuedSFT-3834: fixed lintby Matt Gleason · 54098dfd · May 6, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Matt Gleason

SFT-3834: fixed lint

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 one blank line to satisfy a code linter. It does not change any executable code, logic, or behavior of the Passport firmware.

Security candidateSFT-3834: added verify step for microsd message signing, fixed export format for sparrow parsingby Matt Gleason · 18e80883 · May 6, 2026 · 2 filesMessage 75 · AdequateLow 34Details
Commit message · Matt Gleason

SFT-3834: added verify step for microsd message signing, fixed export
format for sparrow parsing

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundary
AI analysis · Low 34/100

This firmware update fixes two issues in the Passport hardware wallet's message-signing feature. First, it adds a user confirmation screen when signing a message from a microSD card in normal (non-health-check) mode, so the user can see the message and the address that will sign it before approving. Second, it corrects the exported message signature text format so wallet software like Sparrow can parse it properly. Previously, the signature block used generic BEGIN/END SIGNATURE labels instead of blockchain-specific ones, which could cause import failures.

AI review queuedBump actions/checkout from 4 to 6by dependabot[bot] · df28b1ef · Mar 27, 2026 · 2 filesMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]

Bump actions/checkout from 4 to 6

Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v4...v6)

---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: '6'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a routine automated update by Dependabot that changes the version of a GitHub-provided action used to check out source code during automated build and lint workflows. There is no indication of a security issue in the commit itself, and no security relevance is disclosed.

Lower-priorityfixed reuse errors caused by version bump, converted dep5 to tomlby Matt Gleason · 2b30715b · Mar 26, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Matt Gleason

fixed reuse errors caused by version bump, converted dep5 to toml

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 housekeeping change. It removes an old license metadata file (.reuse/dep5) and replaces it with a newer TOML-format file (REUSE.toml). It also updates a build helper script (Justfile) to remove a now-unnecessary command-line flag from the reuse license-linting tool. There is no change to the firmware code that runs on the Passport device, so it cannot directly affect device security or user funds.

AI review queuedBump actions/upload-artifact from 4 to 7by dependabot[bot] · f5ebe556 · Mar 26, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]

Bump actions/upload-artifact from 4 to 7

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 7.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v4...v7)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-version: '7'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that changes the version of a GitHub Actions helper used to store build outputs. There is no indication this change fixes or introduces a security problem in the firmware itself.

AI review queuedBump fsfe/reuse-action from 4 to 6by dependabot[bot] · 719da673 · Mar 26, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]

Bump fsfe/reuse-action from 4 to 6

Bumps [fsfe/reuse-action](https://github.com/fsfe/reuse-action) from 4 to 6.
- [Release notes](https://github.com/fsfe/reuse-action/releases)
- [Commits](https://github.com/fsfe/reuse-action/compare/v4...v6)

---
updated-dependencies:
- dependency-name: fsfe/reuse-action
dependency-version: '6'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that bumps the version of a GitHub Action used to check software licensing (REUSE compliance) from version 4 to version 6. It only affects the project's linting workflow and does not change any firmware code, build outputs, or security-sensitive behavior. There is no indication of a security issue.

AI review queuedBump docker/setup-buildx-action from 3 to 4by dependabot[bot] · a3a2cd05 · Mar 26, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]

Bump docker/setup-buildx-action from 3 to 4

Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3 to 4.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](https://github.com/docker/setup-buildx-action/compare/v3...v4)

---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
dependency-version: '4'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is an automated dependency update by Dependabot that bumps the GitHub Actions 'docker/setup-buildx-action' from version 3 to version 4 in the project's build workflow file. It is a routine maintenance change with no visible security-relevant code modifications.

AI review queuedBump docker/build-push-action from 6 to 7by dependabot[bot] · 32a32a8a · Mar 26, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]

Bump docker/build-push-action from 6 to 7

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6 to 7.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/v6...v7)

---
updated-dependencies:
- dependency-name: docker/build-push-action
dependency-version: '7'
dependency-type: direct:production
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated update by Dependabot that changes the version of a GitHub Actions tool used to build and push Docker images, from version 6 to version 7. There is no indication of a security issue in the commit itself, and no security-related context is provided.

AI review queuedSFT-5689: improved path mismatch logicby Matt Gleason · b8ff1071 · Mar 26, 2026 · 1 fileMessage 45 · ThinLow 42Details
Commit message · Matt Gleason

SFT-5689: improved path mismatch logic

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 42/100

This commit tightens how Passport checks that all inputs in a Bitcoin transaction belong to the same wallet account. Previously, the firmware only compared a partial derivation path prefix, which could have allowed mixing inputs from different wallet types (for example, Native SegWit and Taproot) that share the same account keys. The change now explicitly checks whether the wallet 'purpose' numbers differ and only allows that mismatch for known compatible types (84 for SegWit, 86 for Taproot). This is a defensive hardening fix rather than a clear exploit patch, because the commit message and diff do not describe a demonstrated attack.

AI review queuedSFT-5689: prevented suspicious change alert for transactions from super-accountsby Matt Gleason · 4c76b7c8 · Mar 25, 2026 · 1 fileMessage 65 · AdequateLow 42Details
Commit message · Matt Gleason

SFT-5689: prevented suspicious change alert for transactions from
super-accounts

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 42/100

This firmware update changes how Passport checks whether a Bitcoin transaction's change output looks suspicious. The device previously compared the full beginning portion of the derivation path, which caused false alarms when a user combined Segwit and Taproot accounts under one 'super-account' (where only the first path number, the purpose, differs). The patch ignores that first purpose number when deciding if outputs belong to the same wallet, so legitimate change from mixed-account setups no longer triggers a warning. It is a user-experience fix rather than a clear security bug, but any relaxation of a warning rule deserves review to ensure it cannot hide a real attack.

AI review queuedSFT-6783: fixed check for fully signed transactions with taprootby Matt Gleason · 5ff5e4a3 · Mar 19, 2026 · 1 fileMessage 50 · ThinModerate 58Details
Commit message · Matt Gleason

SFT-6783: fixed check for fully signed transactions with taproot

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 58/100

This firmware update fixes how Passport detects a fully-signed Bitcoin transaction when using Taproot. Previously, the wallet could misjudge whether a Taproot transaction input was already signed, which could lead it to either skip needed signing or misreport the transaction state. The fix explicitly checks for the Taproot key-path signature rather than counting sub-paths.

AI review queuedSFT-6061: fixed lintby Matt Gleason · c4a88714 · Mar 12, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Matt Gleason

SFT-6061: fixed lint

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 adds standard open-source license header comments to a Nix build file. It does not change any code, build logic, or security behavior.

Lower-prioritySFT-3979: added taproot to wallet summaryby Matt Gleason · 95f9f81d · Mar 12, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · Matt Gleason

SFT-3979: added taproot to wallet summary

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

This commit adds a new wallet type option called Taproot (BIP86) to the list of address formats shown in the Passport hardware wallet's wallet summary screen. It is a small user-interface change that lets users see and select Taproot-style Bitcoin addresses. There is no indication in the commit that this fixes or introduces a security vulnerability.

Lower-prioritySFT-6061: reduced environment variable relianceby Matt Gleason · 208ef3d6 · Mar 6, 2026 · 1 fileMessage 45 · ThinInformational 12Details
Commit message · Matt Gleason

SFT-6061: reduced environment variable reliance

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

This commit refactors how environment variables are set in the project's Nix development shell. It moves some variables from a dynamic shell script into static declarations and limits others to Linux only. There is no direct security fix or vulnerability patch here; it is a build-environment cleanup.

Lower-prioritySFT-6061: cleaned up nix shell setupby Matt Gleason · 75b85eb8 · Mar 6, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6061: cleaned up nix shell setup

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

This commit is a routine cleanup of the project's Nix-based developer environment. It moves the build configuration for a MicroPython cross-compiler tool into a separate file, updates a copyright year, and adjusts how compiler hardening and environment variables are set. There is no indication this change fixes or introduces a security vulnerability.