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
17488Commits captured
17116AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17116 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): add new strings for EIP-7702

This commit only adds and updates user-facing text strings (labels, warnings, and confirmation messages) for a new Ethereum feature called EIP-7702. It does not change any code that handles private keys, signing logic, transaction parsing,…

No code logic changesOnly translation/string assets modifiedEIP-7702 feature is user-facing text preparation only in this commit
18f1770cby Roman Zeyde+1595−10396 files
No security note in commit
Open full analysis →Source commit ↗
Informational 22 AI analysisMessage 92 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(prodtest): log Tropic initialization errors

This commit changes how the Trezor hardware wallet's production-test firmware initializes the Tropic secure chip. Previously, the chip was initialized automatically at boot and failures were silently ignored. Now, initialization is done on…

Change from silent boolean init failure to explicit error-code reportingRemoval of boot-time Tropic initialization in production-test firmwareDeletion of `tropic_wait_for_ready()` polling loop
9a0ae88aby Martin Pastyřík+313−18114 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Using also_delete_snapshots parameter

This commit only changes a GitHub Actions CI workflow file. It adds a new optional checkbox that lets maintainers choose to delete outdated test snapshot files when automatically regenerating snapshots during a manual test run. There is no…

b7e86265by Ilya Artemov+6−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 88 · Strong
AQ ACINQEclair BitcoinLightning Network

Ignore repeated invalid `tx_signatures` (#3328)

This update changes how the Eclair Lightning node handles repeated bad 'tx_signatures' messages from a peer during dual-funded channel opens and splices. Previously, every bad signature was processed and logged, which could waste CPU and d…

Rate-limiting of invalid peer messages (tx_signatures) to prevent repeated CPU/disk consumptionRemoval of unnecessary DB writes on shutdown receipt, reducing disk-wear and potential DoS surfaceNo channel force-close on invalid signatures; node remains open and waits for on-chain confirmation
823341e6by Bastien Teinturier+74−402 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
AQ ACINQEclair BitcoinLightning Network

Update Bitcoin Core to v31.1 (#3327)

This commit simply updates Eclair's required Bitcoin Core version from 30.x to 31.1. It changes download URLs, SHA-256 checksums, documentation, a runtime version check, and a test path. There is no security vulnerability in this change it…

cbafa93aby Bastien Teinturier+13−105 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 93 · Strong
AQ ACINQEclair BitcoinLightning Network

Reject `temporary_channel_id` duplicates early (#3324)

This change tightens how Eclair handles incoming Lightning channel requests. It now rejects a new channel's temporary ID if it collides with an existing final channel ID for the same peer, and it re-checks for collisions after rate-limitin…

duplicate identifier collision now rejected earliernon-atomic interceptor step followed by re-checkfinal channel ID included in collision detection
9b0bcec4by Bastien Teinturier+79−572 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

style(core/rust): configure rustfmt for uniform grouping

This commit only changes Rust code formatting rules. It moves a rustfmt.toml configuration file up one directory and adjusts how Rust import statements are automatically grouped and sorted. There is no change to program logic, security beh…

59f6029bby matejcik+4−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

style(core/rust): apply uniform import grouping

This is a purely cosmetic code-style commit. It runs the project's Rust formatter across hundreds of files, changing only how import statements are grouped and how long comments are wrapped. No program logic, security behavior, or function…

035e7fd0by matejcik+3670−5417436 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: create phony target in makefiles

This commit only adds '.PHONY' declarations to many Makefiles. These declarations tell the build system that certain target names are not real files, preventing build mistakes if a file with the same name happens to exist. There is no chan…

40926b8bby Ondřej Vejpustek+110−817 files
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): disable writing MCU attestation certificate in firmware

This commit changes a Trezor firmware function so that, outside of a special factory testing mode (PRODTEST), it refuses to write an MCU attestation certificate. Previously the function accepted and stored such a certificate. The change pr…

Function that writes security-relevant attestation material now returns failure outside factory-test buildsChange is in the secret/secure-storage subsystemNo changelog entry and minimal commit message, suggesting quiet hardening rather than documented bug fix
6d2883bbby Ondřej Vejpustek+6−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): use empty MCU attestation certificate in prodtest

This commit changes how Trezor hardware wallet firmware handles a special factory-testing mode called 'prodtest'. In prodtest builds, it now uses an empty placeholder certificate for MCU (microcontroller) attestation instead of a real devi…

Attestation certificate handling changed in a security-adjacent code pathEmpty/zero-length certificate used in a production-test configurationNo changelog entry provided despite touching security-relevant code
ccb99c5eby Ondřej Vejpustek+11−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): replace `gen.sh` with `generate_certificates.py`

This is a routine developer tooling change. Trezor replaced a shell script used to convert certificate files into C header files with a new Python script that does the same job. The actual certificate data did not change, only the wrapper …

92a5919aby Ondřej Vejpustek+436−35310 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 →