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.

24Projects watched
18168Commits captured
17444AI analyses
103High-risk findings · 30d
The watch feed

Changes worth understanding

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

17444 analyses
Highest risk·RSS
Informational 24 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

keep NFC export tag live for repeated probes

This is a bugfix for the COLDCARD hardware wallet's NFC sharing feature. Previously, when exporting data over NFC, the device would write the tag contents fresh for each tap/scan attempt. Some phones check the tag multiple times before acc…

NFC export reliability fixRepeated NFC probe handlingNDEF tag state persistence
6716fcbaby scgbckbone+13−92 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
KX KruxKrux BitcoinHardware wallets

fix: improve default theme contrast (#879)

This commit adjusts color values in the Krux device's user interface themes to improve text and icon contrast. It is purely a visual accessibility/usability fix and does not change any security-sensitive logic, cryptography, input handling…

782735a6by Naman Gupta+198−225 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Move from_key_and_merkle_root back to taproot-primitives

This commit is a routine internal code reorganization. It moves a helper function that computes a Taproot tweak hash from one module to another and removes an extension trait that was only used to attach that function. There is no security…

4e5407b4by Mitchell Bagot+25−276 files
No security note in commit
Moderate 59 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): typo in tropic.c

A single-word typo in a Trezor hardware-wallet security file meant a safety check did nothing. The code said 'false;' instead of 'return false;', so when a buffer-limit check failed, the function kept running instead of stopping. This coul…

Missing return statement neutralizes a bounds checkSubsequent memcpy may write beyond intended output buffer limitsLocated in secure-element/tropic driver code (core/embed/sec/tropic/tropic.c)
e473dcc3by Martin Pastyřík+1−11 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

docs: architecture documentation

This commit only adds architecture documentation and diagrams to the Trezor firmware repository. There are no code changes, no bug fixes, and no security-related modifications. It is purely a documentation improvement.

d489a974by cepetr+2395−012 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

docs: add details to arch documentation

This commit is a documentation-only change. It renames and expands an architecture document describing how Trezor firmware is structured, how its security boundaries work, and how third-party apps interact with the system. No code, build s…

Documentation-only change with no executable code modificationsNew document describes existing security architecture, including known limitation that coreapp can request raw secretsNo changes to syscall/smcall verifiers, dispatchers, drivers, or isolation configuration
83228b2eby matejcik+437−3952 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(python): remove nrf magic from HeaderType

This is a small code cleanup in Trezor's Python firmware-handling library. It removes an unused firmware header type for Nordic (NRF) chips and renames an internal 'magic' field so it is no longer treated as a user-facing header type. It a…

2e90694fby M1nd3r+3−82 files
No security note in commit
Informational 20 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(python): fix trezor model parsing

This commit fixes a small bug in the Python Trezor library that identifies which Trezor hardware model is being used. Previously, the code would crash when it saw a valid but unrecognized model identifier. The fix makes the parser accept a…

No security-relevant keywords in commit title or messageNo changelog entry providedChange is a parsing/validation fix, not a memory-safety or cryptographic fix
09520872by matejcik+5−11 file
No security note in commit
Informational 21 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/tools): fix `headertool_pq.py`

This commit fixes a developer tool used to prepare Trezor firmware images. Previously, the tool always signed firmware with internal 'dev keys' regardless of user intent. Now it only signs with dev keys when the user explicitly requests it…

Fixes unintended use of development-only signing keysDeveloper tooling bug, not runtime firmware vulnerabilityNo changelog entry provided by vendor
aa55ec2cby matejcik+3−21 file
No security note in commit
Informational 19 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(python): introduce `NrfHeader` and `NrfImage`

This commit adds new Python code to the Trezor firmware tools for parsing and building Nordic Semiconductor (nRF) style firmware images. It is a feature addition, not a fix. The code handles firmware headers, TLV metadata blocks, SHA-256 d…

Adds Ed25519 signature verification for nRF firmware imagesAdds SHA-256 digest computation over header + image data + protected TLVAdds integrity checks on TLV table magics, protected TLV size, and trailer
af1a4b51by M1nd3r+388−13 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: share a single mocked steady clock across FuzzedSock instances

This change only affects Bitcoin Core's internal fuzz testing code. It makes several test mock sockets share a single fake clock instead of each having their own, so timing behaves more realistically during automated fuzz testing. There is…

6fa41322by Hao Xu+45−4011 files
No security note in 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