CommitWatch RSS
Continuous public-repository analysis

Open source.
Not open secrets.

We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.

Explore the watch feed ↓See how scoring works →
24Projects watched
17865Commits captured
17284AI analyses
99High-risk findings · 30d
The watch feed

Changes worth understanding

AI analysis is published as generated. Community notes appear after human validation.

17284 analyses
Highest risk·RSS
Informational 18 AI analysisMessage 72 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Set max fee in route params for probes

This change sets a maximum routing fee for Lightning payment probes. Previously, probes used a dummy RouteParameters object with no fee limit. Now the fee cap is set to the actual fee of the fixed probe path. This is a minor hardening/clea…

Fee budget now enforced/recorded for probe routesRemoval of justification comment for unbounded probe feeDefensive consistency between probe and normal payment route parameters
47f58f34by Valentine Wallace+1−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 55 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Fuzz: remove unnecessary route_params clones

This commit removes two unnecessary .clone() calls on route_params inside a fuzz test file. It is a code cleanup change in test-only code and does not affect production behavior, security, or user funds.

cc4312a7by Valentine Wallace+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: update API files

This commit only updates three text files that list the public API surface of the `bitcoin_hashes` crate. It records two newly added methods (`hash` and `with_input`) on the `HashEngine` trait. There are no code changes, no bug fixes, and …

6c0f1ea5by jrakibi+6−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 60 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: Add with_input method to HashEngine

This commit adds a new convenience method called with_input to the hash engine API. It is purely a quality-of-life change that lets callers chain hash-input calls together. There is no security-relevant change: the existing input method st…

641d75b3by jrakibi+16−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(python): client.ensure_unlocked() works without deriving a session

This is a small optimization in the Trezor Python library. The `ensure_unlocked()` helper used to pick or create a wallet session, which forced the hardware wallet to derive the master seed just to check if the device was unlocked. The new…

No security-relevant keywords in commit title or messageNo CVE, advisory, or vendor security notice referencedChange is framed as a feature/performance optimization in changelog
b56edf29by matejcik+17−202 files
No security note in commit
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 92 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(python): fix trezorctl get-session

This commit fixes the `trezorctl get-session` command in Trezor's Python library. It prevents crashes when an invalid session ID is supplied, ensures a required pairing step is completed when resuming secure (THP) sessions, and changes the…

Invalid input (malformed base64 session ID) previously caused an unhandled exception/crash in the CLI.THP session resumption could leave pairing in an invalid state because `pairing.finish()` was skipped when no pairing flow ran.The `passphrase=False` semantic change could affect which wallet/session is derived in CLI workflows, but the commit message frames this as matching actual intended usage.
fda4ad4bby matejcik+28−492 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

tests: fix expected responses after ensure_unlocked() modification

This is a one-line update to a test file. It changes what the test expects the device to return after a screen unlock step, from a PublicKey message to a Success message. There is no change to the actual device firmware or any security-sen…

83032224by matejcik+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(python): explicitly derive root fingerprint in get_root_fingerprint()

This is a small code-quality fix in the Trezor Python library. The function that reads the hardware wallet's unique root fingerprint now fetches it directly from the device instead of relying on a side effect of the unlock routine. The cha…

Host-side library correctness fixRemoves reliance on side-effect behavior for cryptographic identity valueAdds explicit public-key fetch and bounds-checked 4-byte fingerprint derivation
a4ca63d6by matejcik+4−21 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(python/trezorctl): respect prompt_passphrase when creating a new session

This commit fixes a regression in the Trezor command-line tool (trezorctl). A recent earlier change accidentally removed a shortcut that skips asking the user for their passphrase when the caller explicitly says it is not needed. Because o…

Behavioral regression in authentication flowPassphrase prompt bypass restored for non-wallet operationsNo cryptographic changes or buffer/memory safety issues visible
011a3413by matejcik+16−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

tests: add test for TrezorClient.ensure_unlocked()

This commit only adds and updates automated tests for the Trezor hardware wallet's unlock behavior. It does not change any production firmware, device logic, or security-sensitive code. There is no security issue here.

dcb6938dby matejcik+27−151 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: update UI fixtures

This commit only updates expected test screenshots (called UI fixtures) recorded as cryptographic hashes. The firmware code itself is not changed. The message explains that a helper function called ensure_unlocked() no longer creates a new…

No source code changesOnly test fixture hashes updatedChange is explained as a test-side consequence of a prior behavior change in ensure_unlocked()
05711517by matejcik+95−851 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/eckhart): don't close device menu on `GetFeatures`

This is a user-experience bug fix for the Trezor T3W1 hardware wallet. Previously, asking the device for its basic info (a GetFeatures request) would restart the device's workflow and close any open menu. The fix makes the device ignore th…

No security-relevant signals in diffChange is a UX/workflow behavior fix, not a memory safety, authentication, or cryptographic fixNo input parsing, serialization, or privilege boundary changes
087e7934by Roman Zeyde+27−24 files
No security note in commit
Open full analysis →Source commit ↗
01
Why commit watching?

Security should leave a paper trail.

A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.

Why we built this →