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

AI review queuedSFT-6356: adjusted input already signed messageby Matt Gleason · 6ae0e40b · Mar 2, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6356: adjusted input already signed message

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 · Informational 15/100

This commit is a trivial user-facing string change inside an assertion. It merges two separate 'already signed' error messages into one and updates the text. There is no functional change to how the code behaves, no security fix, and no vulnerability introduced.

Security candidateSFT-4300: added list icon for address explorerby Matt Gleason · 936c1917 · Mar 2, 2026 · 8 filesMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-4300: added list icon for address explorer

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a routine user-interface polish change. It adds a new list-style icon for the 'Explore Addresses' menu item in the Passport hardware wallet firmware, replacing the previous verify-address icon. It also makes two minor build-script tweaks (changing the Python interpreter path from /usr/bin/python3 to /usr/bin/env python3) and adds a missing copyright header to one image file. There is no security-relevant change.

Lower-prioritySFT-6061: fixed simulator camera on waylandby Matt Gleason · f3825636 · Mar 2, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6061: fixed simulator camera on wayland

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

This commit adjusts the software build environment (a Nix flake) for the Passport hardware wallet simulator. It adds two helper graphics libraries and forces the Qt user-interface toolkit to use the X11-compatible 'xcb' backend on Linux when no backend is already chosen. The change only affects how the simulator runs on developer machines, not the real firmware or any user funds.

Lower-prioritySFT-6748: first pass to fix github artifactsby Matt Gleason · e4ea762a · Feb 26, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6748: first pass to fix github artifacts

45/100 · ThinMessage clarity
✓ 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 is a routine GitHub Actions CI/CD maintenance change. It simplifies how firmware build artifacts are named and how bootloader build jobs are configured in the automated build pipeline. There is no change to the firmware code itself, no security fix, and no vulnerability introduced.

Lower-prioritySFT-6061: fixed license on flake.lockby Matt Gleason · 0fa942c8 · Feb 26, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6061: fixed license on flake.lock

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 licensing metadata fix. It adds the file 'flake.lock' to a list of project files that are already declared under the GPL-3.0-or-later license in the REUSE/dep5 configuration. There is no code change, no firmware change, and no security relevance.

AI review queuedSFT-3235: re-enabled btcpay taprootby Matt Gleason · b7fde52a · Feb 26, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · Matt Gleason

SFT-3235: re-enabled btcpay taproot

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 · Informational 19/100

This commit re-enables the option for BTCPay wallet exports on the Passport hardware wallet to use the newer Taproot (P2TR) address format, in addition to the existing SegWit (P2WPKH) format. It is a feature re-enablement, not a fix for a vulnerability. There is no direct evidence in the commit or supplied references that this change addresses a security flaw.

Security candidateSFT-6378: Fix mnemonic_to_bits() and ct_word_eq() to be constant time.by Ken Carpenter · f8311ca7 · Feb 26, 2026 · 3 filesMessage 50 · ThinModerate 60Details
Commit message · Ken Carpenter

SFT-6378: Fix mnemonic_to_bits() and ct_word_eq() to be constant time.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
constant-time or timing behaviorcryptography-sensitive pathboot or update path
AI analysis · Moderate 60/100

This commit fixes a timing side-channel weakness in the code that converts a BIP-39 recovery phrase (a list of words) back into the secret digital bits. Before the fix, the code stopped searching the word list as soon as it found a match and used a normal string comparison, so an attacker measuring tiny time differences might learn which words were entered. The new version always scans the entire word list and compares words in constant time, making the process take the same amount of time regardless of the phrase. A new test checks that timing does not vary with the word positions.

AI review queuedSFT-6507: removed they singlesigby Matt Gleason · 6ddb59b6 · Feb 26, 2026 · 1 fileMessage 45 · ThinInformational 17Details
Commit message · Matt Gleason

SFT-6507: removed they singlesig

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 · Informational 17/100

This commit removes the ability to create a single-signature (single-sig) wallet for the Theya service in the Passport firmware. Only multisig Theya wallets remain supported. There is no indication of a security vulnerability; this appears to be a product or compatibility change.

AI review queuedENV-2282: fixed taproot versions of component hashes when coming after segwitby Matt Gleason · 939b6a29 · Feb 26, 2026 · 1 fileMessage 65 · AdequateHigh 71Details
Commit message · Matt Gleason

ENV-2282: fixed taproot versions of component hashes when coming after
segwit

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 · High 71/100

This firmware update fixes a bug in how Passport hardware wallets compute Taproot Bitcoin transaction signatures. Previously, when a transaction contained both SegWit and Taproot inputs, the wallet could accidentally reuse cached SegWit-style hashes for the Taproot signing math instead of computing fresh Taproot-specific hashes. Because Taproot and SegWit use different hashing rules, this could lead to an invalid signature or, in some edge cases, a signature that does not match what the Bitcoin network expects. The fix creates separate Taproot hash fields so the two paths no longer share state.

AI review queuedENV-2282: fixed taproot sighahes after segwit sighashesby Matt Gleason · 959c4fa6 · Feb 26, 2026 · 1 fileMessage 50 · ThinHigh 70Details
Commit message · Matt Gleason

ENV-2282: fixed taproot sighahes after segwit sighashes

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 · High 70/100

This is a one-line fix in the Bitcoin transaction signing code of the Foundation Passport hardware wallet. When signing a Taproot transaction immediately after signing a SegWit transaction, the wallet could reuse cached intermediate hash values that were not fully initialized for Taproot. That could cause the wallet to compute an incorrect transaction fingerprint (sighash), which in rare cases might lead to an invalid signature or, more seriously, a signature that does not protect all the transaction details it should. The fix forces the wallet to rebuild those cached hashes if any of the required Taproot hash fields are missing.

Lower-prioritySFT-6061: added nixos development instructions to get `just flash` workingby Matt Gleason · 30855dbb · Feb 26, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Matt Gleason

SFT-6061: added nixos development instructions to get `just flash`
working

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates the developer setup guide (DEVELOPMENT.md). It adds instructions for using Nix/NixOS during development, changes the OpenOCD source repository URL from an old fork to the official project, and adds a user to the plugdev group. There is no firmware code change and no security vulnerability is introduced or fixed.

AI review queuedSFT-6061: nix devshell working, sim commands and flash recipe need workby Matt Gleason · bbfb284c · Feb 26, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6061: nix devshell working, sim commands and flash recipe need work

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

This commit updates the project's Nix development environment files. It adds a lock file, adjusts package names, adds build dependencies, and tweaks compiler flags for a local developer tool called 'cosign'. There is no change to the firmware that runs on the Passport device, no change to cryptographic code, and no indication of a security bug or fix.

AI review queuedSFT-6061: incomplete nix shellby Matt Gleason · 52f8ada5 · Feb 26, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-6061: incomplete nix shell

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 · Informational 15/100

This commit adds Nix build environment files (a reproducible developer shell setup) for the Passport firmware project. It does not change any firmware code, cryptographic logic, or device behavior. There is no indication this is a security fix or introduces a security vulnerability.

Security candidateSFT-6727: fixed dangling pointer warning for stack dummiesby Matt Gleason · 19a74faa · Feb 24, 2026 · 3 filesMessage 50 · ThinInformational 18Details
Commit message · Matt Gleason

SFT-6727: fixed dangling pointer warning for stack dummies

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

This commit suppresses a compiler warning about using the address of a short-lived local variable to track the top of the program's stack. The underlying code behavior is unchanged; only the warning is silenced. There is no direct security fix here, though the pattern itself is a known, long-standing MicroPython idiom for estimating stack usage.

Lower-prioritySFT-4397: updated DEVELOPMENT.md to require ubuntu 24.04, suppressed deprecation message in reuse lintby Matt Gleason · 25c4678c · Feb 23, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-4397: updated DEVELOPMENT.md to require ubuntu 24.04, suppressed deprecation message in reuse lint

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 updates developer documentation to say Ubuntu 24.04 is required and adds a command-line flag to silence a deprecation warning in a license-checking tool. It does not change any firmware code, build outputs, or security behavior.

Lower-prioritySFT-4339: ran auto backup after renaming the deviceby Matt Gleason · 97197470 · Feb 23, 2026 · 1 fileMessage 50 · ThinInformational 16Details
Commit message · Matt Gleason

SFT-4339: ran auto backup after renaming the device

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

This commit makes the Passport hardware wallet automatically create a backup after the user renames the device. The change is a functional improvement to ensure the new device name is preserved in backups, not a fix for an exploitable security flaw. There is no indication of a vulnerability or attack scenario.

Lower-prioritySFT-4410: set openocd version in DEVELOPMENT.mdby Matt Gleason · a82245d7 · Feb 23, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Matt Gleason

SFT-4410: set openocd version in DEVELOPMENT.md

45/100 · ThinMessage clarity
✓ 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 is a documentation-only change. It updates the developer setup instructions to clone a specific, released version (v0.12.0) of the OpenOCD debugging tool instead of the latest development code. There is no change to firmware code, no user-facing change, and no security fix or vulnerability introduced.

Lower-prioritySFT-4385: Don't strip Rust debug information.by Jean-Pierre De Jesus DIAZ · 354c61b9 · Feb 23, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4385: Don't strip Rust debug information.

* extmod/foundation-rust/Cargo.toml (profile) <release>: Don't strip
debug information.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit changes a Rust build setting so that debug information is no longer removed from the released firmware. On its own, this is a build/debugging convenience change, not a security fix. It does not patch any vulnerability, change runtime behavior, or introduce a known exploit path.

Security candidateSFT-4441: Update Rust dependencies.by Jean-Pierre De Jesus DIAZ · efd6bdb3 · Feb 23, 2026 · 4 filesMessage 45 · ThinLow 29Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4441: Update Rust dependencies.

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Low 29/100

This commit updates several Rust library dependencies used in the Passport hardware wallet firmware and makes small code adjustments to match the new library versions. The most notable change is in the cryptographic signing code, where the code no longer wraps the data in a 'Message' object before creating a Schnorr signature. On its own, this looks like a routine compatibility update, but because it touches security-critical code (digital signatures), it warrants careful review to ensure the new calling pattern is safe and does not bypass any intended message-validation step.

Lower-prioritySFT-4382: Bump docker/build-push-action.by Jean-Pierre De Jesus DIAZ · 2c2f1855 · Feb 23, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4382: Bump docker/build-push-action.

* .github/workflows/build.yaml: Bump docker/build-push-action from 5 to
6.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates a GitHub Actions helper used to build Docker images from version 5 to version 6. There is no indication of a security fix or vulnerability in the change itself.

Lower-prioritySFT-4357: Use Ubuntu 24.04.by Jean-Pierre De Jesus DIAZ · 314b4487 · Feb 23, 2026 · 2 filesMessage 60 · AdequateInformational 13Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4357: Use Ubuntu 24.04.

* Dockerfile: Update base image to Ubuntu 24.04 (Noble Numbat).
* .github/workflows/build.yaml: Likewise.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 13/100

This commit updates the project's build environment from Ubuntu 20.04 to Ubuntu 24.04 in its GitHub Actions CI workflow and Docker container. It also switches the 'reuse' license-compliance tool from being installed via Python's pip to being installed as a standard Ubuntu package. This is a routine maintenance change. It does not by itself fix a known security vulnerability, but staying on a newer, supported operating-system base reduces long-term risk from outdated dependencies and avoids the end-of-life status Ubuntu 20.04 will reach in April 2025.

Security candidateSFT-4389: Update copyright e-mail address.by Jean-Pierre De Jesus DIAZ · 8c1f220b · Feb 23, 2026 · 728 filesMessage 68 · AdequateInformational 15Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4389: Update copyright e-mail address.

Changes made using:

```
rg 'hello@foundationdevices\.com' --files-with-matches | xargs sed -i 's/hello@foundationdevices\.com/hello@foundation.xyz/g'
```

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This commit is a bulk update of the company's contact email address in copyright headers and documentation. It replaces 'hello@foundationdevices.com' with 'hello@foundation.xyz' across 728 files. There are no code logic changes, no security fixes, and no functional changes to the firmware.

Lower-prioritySFT-4382: Bump fsfe/reuse-action.by Jean-Pierre De Jesus DIAZ · 7b5fd4d1 · Feb 23, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4382: Bump fsfe/reuse-action.

* .github/workflows/lint.yaml (is-reuse-compliant): Bump
fsfe/reuse-action to v4.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates a GitHub Actions linting tool (fsfe/reuse-action) from version 2 to version 4. It only affects the project's automated license/copyright compliance check and does not change any firmware code, build outputs, or user-facing behavior. There is no security relevance visible in the commit.

Security candidateSFT-3834: added microsd message signingby Matt Gleason · e47977e3 · Feb 23, 2026 · 4 filesMessage 45 · ThinInformational 12Details
Commit message · Matt Gleason

SFT-3834: added microsd message signing

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 12/100

This commit adds a new menu option that lets users sign a message using a file stored on a microSD card, alongside the existing option to sign by scanning a QR code. It reuses the same internal signing logic that was already used for health checks, just with different on-screen labels and file filters. There is no indication in the code that this weakens security or introduces a vulnerability; it appears to be a normal feature addition.

Lower-prioritySFT-4357: Increase MSRV to 1.77.1.by Jean-Pierre De Jesus DIAZ · 17033047 · Feb 23, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · Jean-Pierre De Jesus DIAZ

SFT-4357: Increase MSRV to 1.77.1.

* .github/workflows/build.yaml: Increase MSRV to 1.77.1.
* .github/workflows/lint.yaml: Likewise.
* Dockerfile: Likewise.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit simply updates the project's declared minimum Rust compiler version from 1.70.0 to 1.77.1 in CI configuration files and a Dockerfile. It does not change any firmware source code, fix a vulnerability, or alter product behavior. It is a routine build-environment maintenance change.