Every captured commit receives deterministic security triage and a separate communication-quality score. Full patches and Ollama analysis are reserved for ranked candidates.
55candidates55AI analyses
28commits · 30 days
47commits · 60 days
312commits · 180 days
647commits · 365 days
Backfill bands
Aug 5 → Feb 6335 seen28 candidatesComplete
Feb 6 → Jun 6265 seen19 candidatesComplete
Jun 6 → Jul 619 seen5 candidatesComplete
Jul 6 → Aug 526 seen3 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.
This commit fixes a class of low-level memory-safety bugs where Rust code was given buffers containing uninitialized bytes. Rust's rules require every byte of a slice to be initialized, even if the function will overwrite them. Passing uni…
Undefined behavior at C/Rust FFI due to uninitialized buffers being treated as Rust slicesPotential optimizer-dependent behavior from violating Rust slice initialization rulesHardening of cryptographic output paths (SHA-256, HMAC-SHA256, HMAC-SHA512)
This commit fixes a bug in how the BitBox02 hardware wallet wipes files from its SD card. Before erasing a file, the device now checks the file's reported size against a safe maximum. Without this check, a tampered SD card could claim a fi…
CVE-2026-6682 referenced in commit messageMalformed FAT directory entry could cause excessive overwrite loopDenial-of-service via SD card tampering
This update adds a safety check when the BitBox02 hardware wallet mounts a microSD card. A malicious or deliberately malformed FAT filesystem could trick the device's file-system library into placing user data inside attacker-controlled bo…
Fixes integer-wrap / geometry confusion in FAT mount logicAdds explicit post-mount validation of filesystem metadataPrevents data area from landing inside attacker-controlled FAT sectors
This update fixes the BitBox02 bootloader's firmware-erase routine. Previously, when erasing leftover padding after a firmware update, the bootloader started erasing at the exact page where the firmware ended. Because flash memory can only…
Bootloader firmware erase routine could erase a flash block containing both firmware and paddingFix aligns erase start to erase-block boundary and re-checks erased state before erasingChangelog describes the change as a fix for 'partially erased flash blocks'
This commit adds production bootloader upgrade files for the BitBox02 hardware wallet and updates build scripts to use them. It is a routine asset-management change: replacing placeholder development hashes with real signed production bina…
This commit fixes a build script used only for development/testing versions of the BitBox02 bootloader upgrade. It makes the development-stage1 bootloader images unsigned again, while keeping production images fully signature-verified. The…
Signature verification relaxed only for development buildsProduction payload validation still requires signaturesDevelopment stage0 already skipped stage1 signature verification per commit message
This commit fixes a bootloader bug where the device rejected firmware updates that used the maximum allowed size. The off-by-one check meant legitimate full-sized firmware images could not be installed, potentially blocking updates. The fi…
Off-by-one input validation in firmware-update pathBootloader change affecting firmware chunk count acceptanceCHANGELOG labels the change as a bugfix for full-sized firmware upgrades
This is a large firmware commit that adds a new two-stage bootloader update mechanism for the BitBox02 hardware wallet. It replaces the old single bootloader with a small, fixed 'stage0' plus a separately signed 'stage1', and ships a speci…
Bootloader architecture changed from monolithic to two-stage (stage0 + signed stage1).Firmware signature hash now includes a 16-bit product_id, binding firmware to product variant.Root public keys were rotated/replaced with a single set across all products.
This commit is a routine maintenance update for the BitBox02 hardware wallet firmware. It upgrades the pinned Rust compiler toolchain from an older version to Rust 1.96.0, updates the project's Docker build container and related developer …
Routine toolchain and dependency upgradeVendored libc updated across many platform bindingsNo first-party security-relevant code changes
This commit removes the use of the standard snprintf formatting function from the BitBox02 bootloader's developer menu and replaces it with a small, fixed-format helper. The main goal is to reduce the bootloader's binary size and make the …
Removes snprintf/printf usage from bootloader code, reducing binary bloat and eliminating a complex formatting library from a privileged execution contextExtends automated CI check to detect stdio/Rust formatting symbols in regular development and production bootloader outputs, not just production buildsAdds unit test coverage for the new fixed-format helper
This commit removes the use of standard string-formatting functions (like snprintf and Rust's format!) from the bootloader and related low-level code, replacing them with smaller, fixed-size string builders. The stated goal is to reduce bi…
Removal of stdio formatting (snprintf family) from bootloader codeRemoval of Rust format!/write! formatting from bootloader-linked codeAddition of CI gate rejecting stdio and Rust formatting symbols in production bootloader ELFs
This commit is a simple code cleanup: it moves a handful of string-formatting helpers (for pairing codes, progress percentages, hash display, timers, and unknown-command messages) out of the main bootloader file into a new dedicated file, …
This commit removes a 100-character stack buffer and passes bootloader messages straight to the screen-drawing function. The old code used snprintf to copy the message into a fixed-size buffer, which could silently truncate very long strin…
Removal of fixed-size stack buffer in bootloader display pathElimination of snprintf with potentially attacker-influenced format string argumentBootloader code touched, which is a security-sensitive component
This commit replaces floating-point progress calculations with integer math to save firmware space. It removes the use of f32 arithmetic for progress bars in Bitcoin transaction signing and Bluetooth firmware upgrades. There is no direct s…
Removal of floating-point arithmetic reduces attack surface related to soft-float emulation bugsNew integer fraction API introduces denominator-non-zero and numerator-bound assumptionsCall sites use checked arithmetic to prevent overflow in progress computation
This commit changes the build system to enable Link-Time Optimization (LTO), a compiler technique that shrinks the final firmware size. It also adds safeguards to keep the stack protector security feature working under LTO and deliberately…
Build-system change enabling LTO with explicit stack-protector symbol retentionDeliberate exclusion of bootloader, factory-setup, ASF4, samd51a-ds, and embedded-swd from LTO due to audit complexityToolchain switch to LTO-aware archive utilities to avoid invalid tiny images from missing live objects
This commit is a code refactoring that moves the device attestation signing function from C code into Rust code. It converts the function to be asynchronous (async/await) and rewrites the parsing of the secure chip's DER-encoded signature …
Removal of C synchronous secure chip signing wrapperAddition of async Rust secure chip ECDSA signing operationRelocation of DER signature parsing from C-API Rust crate into securechip crate
This commit is a build-system and code-organization refactor. It moves the automatically generated Rust protobuf message definitions from inside the main bitbox02-rust crate into a new, separate bitbox-proto crate. It also switches the gen…
This commit is a code cleanup in the BitBox02 firmware's Rust code. It changes how random numbers are supplied when creating cryptographic keys for the Noise protocol, moving from a device-specific random type to a more generic hardware ab…
Refactor of cryptographic randomness plumbing for Noise/X25519 key generationRemoval of device-specific RNG trait in favor of HAL random abstractionResponder ephemeral key now generated explicitly before handshake state creation
This commit changes how the BitBox02 hardware wallet warns users about very large Ethereum transaction data and typed messages. Previously, large transaction data was shown only as a byte count with the message 'too large to display.' Now …
UI warning consistency change for large Ethereum dataShared preview/truncation logic between eth transaction and typed-message signingStreaming data producer now captures a bounded preview while hashing
This commit is a code-quality refactor for unit tests only. It introduces a small Rust helper macro called async_test::test that lets developers write async test functions directly, instead of manually wrapping async code in a block_on() c…
Reject backup data whose declared seed length exceeds the fixed 32-byte seed field. This prevents malformed SD-card backups from triggering an out-of-bounds panic while listing backups.
Add a regression test with an otherwise valid protobuf and recomputed checksum.
Tests: - `cargo test --manifest-path src/rust/Cargo.toml --all-features -- --test-threads 1` - `./scripts/dev_exec.sh make run-unit-tests`
90/100 · StrongMessage clarity
✓ 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
defensive validationfuzzing or regression evidence
Reject policy keys whose rendered confirmation exceeds the UI label limit. This prevents registration from approving a key that cannot be displayed in full.
Add boundary coverage for a 640-byte key and rejection at 641 bytes.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Routine changebb03 ui: replace long touch with slide to confirmby Jad · cc6ae75d · Aug 3, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Jad
bb03 ui: replace long touch with slide to confirm
replaces hold to confirm (long touch) with slide to confirm and removed long touch for BB03
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Routine changebb03 UI: slide to confirmby Jad · 30a68c8d · Aug 3, 2026 · 11 filesMessage 68 · AdequateTriage 0Details
Commit message · Jad
bb03 UI: slide to confirm
Implement slide to confirm UI component for confirming transactions and sensitive operations
Delete render_slide_confirm.rs
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Read the confirmation result before clearing CONFIRM_STATE. The result reference points into GroundedCell storage, so clearing the state first invalidates it before result.is_ok() reads it.
This keeps the poll contract: publish the completed result, clear the task state, and report completion. It also matches rust_workflow_unlock_poll().
Rust slices require every byte in their backing storage to be initialized, even when a function only intends to overwrite the bytes. Several C callers passed uninitialized output buffers through BytesMut, and SHA/HMAC created mutable slices directly from such pointers. This was formal UB and could allow optimizer-dependent behavior.
In practice, these paths only wrote their outputs before C consumed them, and current builds emitted the expected stores. No secret disclosure, corrupted output, or control-flow impact was observed. This is hardening rather than a fix for a demonstrated exploit.
Initialize C storage before constructing BytesMut. Keep output-only helpers on raw pointers so they can legally initialize storage, and document the FFI invariant. Raw-pointer APIs that already used direct stores remain valid.
73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was security-ranked
explicit security languagedefensive validationcryptography-sensitive pathboot or update pathparser or protocol path
AI analysis · Low 39/100
This commit fixes a class of low-level memory-safety bugs where Rust code was given buffers containing uninitialized bytes. Rust's rules require every byte of a slice to be initialized, even if the function will overwrite them. Passing uninitialized memory could let the compiler make unsafe assumptions, but the commit message says no actual exploit or data leak was observed. The fix initializes buffers before handing them to Rust and switches some helpers to use raw pointers so they can legally write into uninitialized memory.
Reject schemas and values whose recursive struct or array traversal exceeds a bounded depth. Validate type roots before callbacks and cover the boundaries with tests.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Replace the unbounded concurrent queue with a fixed-capacity ring buffer storing 16 Runnable slots inline. Scheduling no longer allocates, including when wakers run in interrupt context.
Limit active tasks to the queue capacity so exhaustion is reported from spawn rather than from a waker. Protect queue access with critical sections because wakers and the main loop may access it concurrently.
The executor currently has three normally serialized root-task sources, so 16 slots leave room for future concurrency and consume 64 bytes on the 32-bit firmware target.
Cover repeated slot reuse and enforcement of the task limit. Remove the now-unused concurrent-queue dependency.
The polling executor ignores wake notifications and is polled on every main-loop iteration. Use core's static no-op waker so ISR callbacks cannot free an Arc while the heap allocator is active.
Remove the now-unused heap-backed waker helper.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Track detached U2F workflow lifetimes independently of their public result state. Return HWW_RSP_BUSY before starting an HWW request while a U2F workflow can still own the shared UI.
This prevents HWW session reset and cancellation paths from invalidating live U2F UI objects. Add regressions for the lifetime guard and busy response.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Async operations can leave the screen stack temporarily empty between two UI calls. This caused the waiting screen to flash, unlike the old synchronous securechip behavior.
Treat locally processing USB requests as active UI work and keep the last frame when no component is stacked. Host waits, screensavers, and explicit components continue to render normally.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context