CommitWatch RSS
BS
← All projectsBlockstream

Blockstream Jade

Firmware for Jade and Jade Plus Bitcoin hardware wallets.

BitcoinHardware walletsElevated watch
Source repository ↗
Repository coverage

414 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Full patches and Ollama analysis are reserved for ranked candidates.

57candidates57AI analyses
10commits · 30 days
67commits · 60 days
198commits · 180 days
414commits · 365 days
Backfill bands
Aug 5 → Feb 6216 seen38 candidatesComplete
Feb 6 → Jun 6131 seen9 candidatesComplete
Jun 6 → Jul 657 seen10 candidatesComplete
Jul 6 → Aug 510 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.

57/100 average clarity
32Strong · 80–100
147Adequate · 60–79
203Thin · 40–59
32Opaque · 0–39
3security 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.
Jon Griffiths2753232157
Mike Tolkachev311010155
Mihailo Milenkovic877057
Daniel Newton6555055
Jamie C. Driver522053
cmiguelrn111045
Gustavo Cateim700079
Austin-Fulbright400060
odudex200071
Sandmann200062
oroderico200048
Valerio Vaccaro200045
Analysis record

Published AI watches

Last scanned 23 minutes ago

Low 42 AI analysisMessage 95 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

Liquid (taproot): add sign_liquid_tx genesis blockhash support

This commit changes how Blockstream Jade handles the 'genesis blockhash' when signing Liquid transactions. Previously, the device only accepted the network's built-in genesis hash. Now it lets users provide a custom genesis hash for test n…

Adds input validation for caller-supplied genesis blockhashPrevents mainnet genesis hash from being used on Liquid test networksRestricts genesis_hash parameter to Liquid networks only
888eff30by Jon Griffiths+82−264 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: rename get_boolean to get_bool

This commit is a simple rename of two internal helper functions from `rpc_get_boolean`/`rpc_get_boolean_or` to `rpc_get_bool`/`rpc_get_bool_or`, updating all call sites accordingly. There is no change to what the code does, no bug fix, and…

f6e946acby Jon Griffiths+24−2518 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: refactor app code to use getters with default values

This commit is a straightforward code cleanup that replaces verbose 'read this optional value, or leave the default' patterns with shorter helper functions that do the same thing. There is no change in behavior and no security issue visibl…

b6a07147by Mike Tolkachev+22−348 files
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 74 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

build: annotate functions returning error codes to ensure they are checked

This commit is a preventive build-hardening change. It adds compiler annotations (WARN_UNUSED_RESULT) to many functions that return success/failure codes, so the compiler will warn if a caller ignores the result. The goal is to catch futur…

Compiler annotation added to enforce checking of error-returning functionsNo specific vulnerability fixed in the diffNo functional code changes or call-site fixes included
909a89aaby Mike Tolkachev+215−15225 files
No security note in commit
Open full analysis →Source commit ↗
Low 42 AI analysisMessage 28 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: fix path size

This commit fixes a small but meaningful bug in how Jade, a hardware wallet, reads key paths from Bitcoin PSBT data. The code was passing the byte size of a buffer when it should have passed the number of 32-bit entries. Depending on how t…

Buffer-size semantic mismatch in security-critical PSBT parsingUse of sizeof() on uint32_t array where element count is expectedCode path involved in 2of3 multisig recovery key identification
9e0c3747by Mike Tolkachev+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_psbt: add early reject on wrong genesis blockhash

This commit fixes a bug in the Blockstream Jade hardware wallet's PSBT (Partially Signed Bitcoin Transaction) signing code. Previously, when the transaction's genesis block hash did not match the expected network, the code set an error mes…

Missing return in error path allows execution to continue after validation failureCross-network genesis hash mismatch not enforced as a hard failurePSBT signing logic accepts mismatched network parameters
56e130b0by Mike Tolkachev+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 42 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

main: fix error handling during PIN change

This commit fixes a bug in the PIN-change flow on Blockstream Jade hardware wallets. Previously, if re-encrypting the wallet keys with a new PIN failed, or if the user abandoned the PIN change, the code did not jump to cleanup as intended.…

Missing error-path control flow in cryptographic key handlingPotential use of stale or partially initialized key material after PIN-change failureCleanup bypass in sensitive authentication code path
64c30823by Mike Tolkachev+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

attestation: harden error handling of challenge signing

This commit fixes a bug in the Blockstream Jade hardware wallet's attestation signing process. Previously, if signing the attestation challenge failed, the device would send an error message but then continue running the rest of the functi…

Missing return after error path allows fall-through to success-path replyUninitialized output.ext_signature_len could leak stack data or cause undefined behaviorAttestation signing failure could result in sending an invalid attestation reply
ecc5871bby Mike Tolkachev+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 39 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

attestation: fix missing cleanup on failed efuse write

This commit fixes a small but real bug in the device attestation setup code for Blockstream Jade, a hardware crypto wallet. When a one-time programmable security fuse failed to burn, the code used to exit immediately without releasing memo…

Missing cleanup on error path in security-critical initializationResource leak on failed efuse writePotential inconsistent attestation state after partial initialization
d37d88b7by Mike Tolkachev+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 77 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

wallet: fix unhandled wrong asset in wallet summaries

This commit fixes a bug in the Blockstream Jade hardware wallet where a function that tracks assets during transaction signing could fail silently. Previously, if an unexpected or wrong asset was encountered while building a summary of tra…

Unchecked return value from asset_summary_update() in signing pathPotential bypass of asset/balance validation during transaction signingWrong or unknown asset could be silently dropped from wallet summaries
b33cf02bby Mike Tolkachev+18−53 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 85 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign: update output logic, rename and document output flags for clarity

This commit reworks how a Blockstream Jade hardware wallet labels transaction outputs. The key change is that the 'change' flag is now only set when the output is also confirmed as belonging to the wallet ('is ours'). Previously, downstrea…

Change output flag now gated by wallet-ownership flagUI hides change outputs based on single bit with runtime assertionGreen 2of3 outputs no longer marked as change because not marked as wallet-owned
cf79a3aaby Mike Tolkachev+32−245 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 58 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

esp-idf: update to v5.5.4, take multisig bootloader component from https://github.com/Blockstream/esp-idf/tree/securebootv2_multisig_v5.5.4

This is a large update that pulls in Espressif's ESP-IDF v5.5.4 bootloader code, plus Blockstream's own multi-signature secure-boot patches. Most of the visible changes are routine: support for newer ESP32 chips, larger flash sizes, and a …

Anti-fault-injection assertion (ESP_FAULT_ASSERT) added around TEE flash address validationTEE flash write/erase now rejects operations targeting the active TEE partition rangeSecure Boot V2 extended to support ECDSA-P384 / SHA-384 digests
d931d543by Daniel Newton+3879−1437104 files
No security note in commit
Open full analysis →Source commit ↗
High 72 AI analysisMessage 85 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_tx: suppress validation/change attribution for green 2of3 outputs

This update fixes a security gap in how Blockstream Jade signs Bitcoin transactions for a specific wallet type called Green 2of3. Previously, the device trusted the connected app to supply a recovery public key and might silently treat an …

Host-supplied recovery_xpub was trusted for change attributionChange output could be misattributed without user confirmationFix suppresses automatic validation for Green 2of3 outputs
0243f239by Mike Tolkachev+17−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

ui: tidy up message/error activities

This commit is a straightforward code cleanup. It replaces a verbose way of showing on-screen messages and errors with simpler helper functions, and fixes a spelling mistake ('re-encypt' to 're-encrypt'). There is no change to security log…

No security-relevant logic changesRefactoring only: API simplification for UI message displaySpelling correction in user-facing error string
1914ace0by Daniel Newton+162−24625 files
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

wire: reduce stack usage sending replies

This commit changes how message context is passed between functions in the Blockstream Jade hardware wallet firmware. Instead of copying the entire message context structure on the stack, functions now receive a pointer to it. The stated g…

Stack usage reduction in embedded firmwarePointer passing instead of structure copyingNo direct vulnerability described in commit message
c41f5fddby Jon Griffiths+65−6429 files
No security note in commit
Open full analysis →Source commit ↗
Informational 24 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: add show_bip85_bip39_entropy RPC command

This commit adds a new device command that lets a connected computer or phone ask a Blockstream Jade hardware wallet to display an encrypted BIP85 seed-entropy backup as a QR code. The change also tightens validation of the BIP32 index in …

New RPC exposes encrypted BIP85 entropy via on-device QR displayBIP32 index bounds checks added in multiple RPC parameter parsersSensitive stack buffers now marked with SENSITIVE_PUSH/POP in QR reply path
3392661cby Daniel Newton+115−277 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: always confirm green outputs when recovery signing

This commit changes the logic in Blockstream Jade's PSBT signing flow so that, when the hardware wallet is acting as a 'recovery' key for a Green 2-of-3 wallet, it always asks the user to confirm outputs that belong to Green, rather than s…

Logic inversion in authorization/confirmation pathRecovery-key signing path previously trusted Green-classified outputs without user confirmationComment explicitly frames change around inability to verify output ownership in recovery path
a963f628by Jon Griffiths+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 58 AI analysisMessage 78 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

attestation: ensure attestation provision signature is correctly sized

This update fixes a check in the Blockstream Jade hardware wallet's attestation setup. Before the fix, the code did not verify that an externally-provided signature was small enough to fit into its storage buffer. A too-large signature cou…

Missing length check before fixed-size buffer usePotential stack/buffer overflow in signature verification pathAttestation/trust-anchor initialization code modified
b6ca54dbby Jon Griffiths+5−71 file
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 73 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

ui: add a better UI for index selection vs PIN entry

This commit is a user-interface refactor for the Blockstream Jade hardware wallet. It replaces a PIN-only digit-entry screen with a shared 'digit entry' widget that can also accept shorter numeric indices (for things like BIP85 child mnemo…

UI-only refactor with no change to PIN size, PIN validation, key derivation, or storageNew index-entry mode allows shorter numeric input, bounded by existing caller-side maximum checksNo buffer size changes: arrays remain DIGIT_ENTRY_SIZE (6) bytes
c78995b6by Daniel Newton+422−3829 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_psbt: add 2of3 recovery path comment for is_green_multisig_signers

This commit only adds a code comment explaining an existing limitation in how Blockstream Jade detects Green multisignature transactions. No code behavior changes. The comment documents that for a specific 2-of-3 recovery wallet setup, the…

Comment-only change with no functional code modificationDocuments a known behavior/limitation rather than fixing a vulnerabilityStates that signing still works correctly in the described fallback case
34f3d162by Mihailo Milenkovic+9−01 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

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

Routine changehardware: add Jade Plus design filesby bitcoinhelp · 5ad85661 · Aug 5, 2026 · 20 filesMessage 68 · AdequateTriage 0Details
Commit message · bitcoinhelp

hardware: add Jade Plus design files

Adds the open source hardware files for Jade Plus, and groups each board's files into its own subdirectory so the two sets aren't interleaved in one flat folder.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Routine changewally: update wally to release 1.5.6by Jon Griffiths · cfce08ce · Jul 11, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

wally: update wally to release 1.5.6

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Routine changepower: release PMU devices before deleting the i2c bus on M5CoreS3by Gustavo Cateim · fb3a009a · Jul 11, 2026 · 1 fileMessage 100 · StrongTriage 8Details
Commit message · Gustavo Cateim

power: release PMU devices before deleting the i2c bus on M5CoreS3

Since ESP-IDF v5.5 i2c_del_master_bus() refuses to delete a bus that
still has devices attached and returns ESP_ERR_INVALID_STATE. On the
M5CoreS3, power_init() attaches the axp2101 and aw9523 devices and
then deletes the bus without releasing them, so under IDF 5.5.4 the
deinit fails, power_init() propagates the error and the JADE_ASSERT
in main.c aborts the boot. Same root cause as the touchscreen fix in
the previous commit (#306).

Remove both devices from the bus before deleting it.

Not tested on hardware (none available); the change mirrors the
touchscreen fix validated on the Waveshare S3 Touch LCD 2.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was security-ranked
defensive validation
Routine changeinput: release touch handles before deleting the i2c busby Gustavo Cateim · 36776fec · Jul 11, 2026 · 1 fileMessage 86 · StrongTriage 25Details
Commit message · Gustavo Cateim

input: release touch handles before deleting the i2c bus

Since ESP-IDF v5.5 (espressif/esp-idf@e73d78ba) i2c_del_master_bus()
refuses to delete a bus that still has devices attached and returns
ESP_ERR_INVALID_STATE. The touchscreen task registers a panel IO
device on the bus but never releases it, so under IDF 5.5.4 the first
touchscreen_deinit() fails and aborts via ESP_ERROR_CHECK.

On boards that panic with PRINT_HALT, such as the Waveshare S3 Touch
LCD 2, this freezes the device on the boot splash screen while
gathering camera entropy, and also hangs the QR scanner and the
camera exit path, since the touchscreen is restarted around every
camera start/stop (see #306).

Releasing the touch handle and the panel IO device (which removes it
from the bus) before deleting the bus restores the deinit/init cycle,
and also fixes a heap leak present under IDF 5.4 where both handles
leaked on every cycle.

Co-authored-by: oroderico <oroderico@users.noreply.github.com>

86/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was security-ranked
entropy or randomness
Routine changediy: Add M5StickC Plus2 backlight brightness controlby oroderico · 5c22b7d3 · Jul 10, 2026 · 4 filesMessage 50 · ThinTriage 0Details
Commit message · oroderico

diy: Add M5StickC Plus2 backlight brightness control

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Routine changerepo: remove stray cUR submodule gitlinkby odudex · 88d69aa6 · Jul 8, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · odudex

repo: remove stray cUR submodule gitlink

Commit 121adaad was cherry-picked from a branch where components/cUR is a proper submodule, and accidentally carried the cUR gitlink along without a matching .gitmodules entry. This breaks 'git submodule update --init' with "no submodule mapping found in .gitmodules for path 'components/cUR'".

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Routine changejade_cli: add selfcheck commandby Jon Griffiths · 32d3c9a7 · Jul 8, 2026 · 1 fileMessage 35 · OpaqueTriage 0Details
Commit message · Jon Griffiths

jade_cli: add selfcheck command

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Routine changelibjade: accept non-literal tags in mocked ESP_LOG macrosby odudex · 121adaad · Jul 8, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · odudex

libjade: accept non-literal tags in mocked ESP_LOG macros

k_quirc logs with a 'static const char* TAG' tag, which the mocked
macros could not handle as they pasted the tag as a string literal.
Print it via %s instead, fixing the libjade host build.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Routine changeAdd TTGO T-Display backlight brightness controlby oroderico · b28e145c · Jul 8, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · oroderico

Add TTGO T-Display backlight brightness control

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Routine changeci: avoid downloading artifacts for non-flash testingby Jon Griffiths · d786cefa · Jul 8, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · Jon Griffiths

ci: avoid downloading artifacts for non-flash testing

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Routine changedocs: update sign_tx docs to include genesis_hashby Jon Griffiths · b937de6f · Jun 29, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Jon Griffiths

docs: update sign_tx docs to include genesis_hash

Also remove trailing spaces for consistency.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was security-ranked
documentation-only discount
Security candidateLiquid (taproot): add sign_liquid_tx genesis blockhash supportby Jon Griffiths · 888eff30 · Jun 29, 2026 · 4 filesMessage 95 · StrongLow 42Details
Commit message · Jon Griffiths

Liquid (taproot): add sign_liquid_tx genesis blockhash support

Allow providing the genesis blockhash for sign_liquid_tx in
addition to the already existing sign_psbt support for PSET.

For test networks, do not require that the provided genesis blockhash
matches the network genesis blockhash. This allows signing for e.g.
custom regtest environments. Ensure that test network signing cannot
use the mainnet genesis blockhash in order to prevent spoofing.

Suggested-by: topologoanatom <survisysy@gmail.com>

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was security-ranked
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit changes how Blockstream Jade handles the 'genesis blockhash' when signing Liquid transactions. Previously, the device only accepted the network's built-in genesis hash. Now it lets users provide a custom genesis hash for test networks (like regtest), but blocks attempts to use the real Liquid mainnet genesis hash on test networks to prevent spoofing. The change also applies the same validation to both PSBT/PSET signing and raw transaction signing. It appears to be a hardening/feature addition rather than a fix for an active exploit, but it does close a spoofing path on test networks.

Routine changeci: run only one qemu job per physical boxby Jon Griffiths · 18fdfd07 · Jun 25, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Jon Griffiths

ci: run only one qemu job per physical box

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Routine changerpc: annotate functions returning error codes to ensure they are checkedby Mike Tolkachev · 517075ba · Jun 25, 2026 · 5 filesMessage 62 · AdequateTriage 12Details
Commit message · Mike Tolkachev

rpc: annotate functions returning error codes to ensure they are checked

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was security-ranked
signing or wallet path
Routine changerpc: rename get_uint64_t to get_uint64by Jon Griffiths · 8e0de45e · Jun 25, 2026 · 7 filesMessage 45 · ThinTriage 12Details
Commit message · Jon Griffiths

rpc: rename get_uint64_t to get_uint64

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was security-ranked
signing or wallet path
Security candidaterpc: rename get_boolean to get_boolby Jon Griffiths · f6e946ac · Jun 25, 2026 · 18 filesMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

rpc: rename get_boolean to get_bool

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was security-ranked
signing or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is a simple rename of two internal helper functions from `rpc_get_boolean`/`rpc_get_boolean_or` to `rpc_get_bool`/`rpc_get_bool_or`, updating all call sites accordingly. There is no change to what the code does, no bug fix, and no security relevance.

Routine changerpc: add alternative typed getters with default valuesby Mike Tolkachev · 23993a22 · Jun 25, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Mike Tolkachev

rpc: add alternative typed getters with default values

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidaterpc: refactor app code to use getters with default valuesby Mike Tolkachev · b6a07147 · Jun 25, 2026 · 8 filesMessage 50 · ThinInformational 15Details
Commit message · Mike Tolkachev

rpc: refactor app code to use getters with default values

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was security-ranked
signing or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is a straightforward code cleanup that replaces verbose 'read this optional value, or leave the default' patterns with shorter helper functions that do the same thing. There is no change in behavior and no security issue visible in the diff.

Routine changeassets: improve precision checkingby Mike Tolkachev · fd0f625d · Jun 25, 2026 · 3 filesMessage 35 · OpaqueTriage 12Details
Commit message · Mike Tolkachev

assets: improve precision checking

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was security-ranked
signing or wallet path
Routine changeconfigs: enable overall stack smashing protection for production devicesby Mike Tolkachev · 0d8422da · Jun 25, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Mike Tolkachev

configs: enable overall stack smashing protection for production devices

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Routine changedocker: update jade_builderby Jon Griffiths · 00e7a397 · Jun 23, 2026 · 4 filesMessage 35 · OpaqueTriage 0Details
Commit message · Jon Griffiths

docker: update jade_builder

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Routine changegui/camera: stop the gui task from possibly trying to render an image from a camera task stack that no longer existsby Daniel Newton · c51f7fb9 · Jun 23, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · Daniel Newton

gui/camera: stop the gui task from possibly trying to render an image from
a camera task stack that no longer exists

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Routine changelibjade: add camera/input/nvs support, refactorby Daniel Newton · f7184945 · Jun 23, 2026 · 32 filesMessage 78 · AdequateTriage 10Details
Commit message · Daniel Newton

libjade: add camera/input/nvs support, refactor

Use libjade-specific rpc calls to handle gui/input/nvs and camera
support. Update the gui example to allow exercising nvs/camera
functionality and optionally running libjade in daemon mode (i.e.
out-of-process).

Add a python console to the gui example to allow programmatic
control of the running jade instance for testing.

Remove config for building without gui support; gui code is now always
built-in regardless of whether a client chooses to fetch the screen
contents for display or not.

Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was security-ranked
authentication path
Routine changedeps: update cbor2 to 6.1.2by Jon Griffiths · 2c602b52 · Jun 23, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

deps: update cbor2 to 6.1.2

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was security-ranked
documentation-only discount
Routine changeFix M5StickC Plus 2 PIN navigationby roderico · 9de1409e · Jun 23, 2026 · 1 fileMessage 45 · ThinTriage 18Details
Commit message · roderico

Fix M5StickC Plus 2 PIN navigation

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was security-ranked
access control