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.

23Projects watched
16902Commits captured
16836AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16836 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: add generated mnemonic flow screenshots

This commit only updates user documentation. It adds new screenshots showing how to create a new wallet mnemonic and updates the script that automatically generates those screenshots. There are no code changes that affect security.

61807e7eby Naman015+39−38 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

refactor: extract wallet info menu helper

This commit is a simple code cleanup: it pulls duplicated code for drawing a wallet information screen into a single reusable helper function. There is no change to what the program does, no new behavior, and no security issue visible in t…

1b068748by odudex+41−441 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

docs(core): update EIP-7702 changelog entry

This commit only edits changelog text. It adds a more precise description of an already-released Ethereum feature (EIP-7702 support) and removes an older, less accurate changelog line. No code, transaction logic, or cryptographic behavior …

d12287b5by Roman Zeyde+1−12 files
No security note in commit
Informational 15 AI analysisMessage 87 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core/ethereum): don't duplicate "skip_models" for EIP-7702 tests

This commit only changes a test data file. It removes duplicate 'skip_models' entries from Ethereum EIP-7702 test fixtures so that the T2T1 model is no longer excluded from these tests. There is no change to firmware code, no security fix,…

1f20560eby Roman Zeyde+0−81 file
No security note in commit
Low 36 AI analysisMessage 98 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): support EIP-7702 authorization/revocation

This commit adds support for signing Ethereum EIP-7702 authorizations and revocations on Trezor hardware wallets. EIP-7702 lets an Ethereum account temporarily delegate control to a smart contract. The code adds a new signing workflow, use…

New cryptographic signing path for EIP-7702 authorization tuplesHard-coded delegate allowlist restricts authorization to known contractsStrict safety checks block authorization but allow revocation
0cd72f03by Roman Zeyde+1130−015 files
No security note in commit
Informational 2 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore(Embit): bump to fff7ffa

This commit is a routine dependency update that bumps the bundled 'embit' library to a newer commit. No actual code changes are shown, and no security relevance is stated in the commit message or title.

77fc9698by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tools): bump-version: support X.Y.Z.W, regen error_codes.json

This is a routine maintenance update to an internal developer tool that bumps software version numbers. It adds support for four-part version numbers, fixes a Python path, and makes the script regenerate an error-codes file after updating …

010a3c41by Martin Milata+56−481 file
No security note in commit
Low 32 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): adding some more simple types.

This commit adds support for more Ethereum data types in Trezor's clear signing feature. It introduces parsing for signed 160-bit integers (int160) and fixed-size byte arrays of various lengths (bytes4, bytes8, bytes16, bytes20, bytes32). …

New parser factory functions include explicit bounds and padding validationSigned integer parser checks two's complement sign-extension paddingFixed-bytes parser validates trailing zero padding per Solidity ABI spec
1e146d45by PrisionMike+181−578 files
No security note in commit
Informational 12 AI analysisMessage 60 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

tests: check liquidity hints are updated for all htlcs

This commit only adds new automated tests for Electrum's Lightning payment routing code. It checks that internal 'liquidity hints' correctly track in-flight payment parts and are cleaned up after multipart payments succeed or time out. The…

2f82eca1by f321x+33−02 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

lnworker/lnrouter: update liquidity hints in htlc callbacks

This commit fixes a bug in Electrum's Lightning payment routing. Previously, when a multi-part payment succeeded, only the first successful payment chunk properly updated the wallet's internal channel-liquidity bookkeeping. Later chunks we…

Resource/accounting leak in routing stateIncorrect penalty of successful Lightning routesPotential denial-of-service against local payment reliability
b176c50aby f321x+8−122 files
No security note in commit
Low 30 AI analysisMessage 76 · Adequate
AQ ACINQEclair BitcoinLightning Network

Accept Bolt12 invoices with reply path (#3325)

This commit loosens Eclair's validation of BOLT12 invoice onion messages so that invoices may now include a reply path. Previously, Eclair rejected invoices that carried a reply path, which caused compatibility problems with LDK nodes. The…

Loosened TLV validation for BOLT12 Invoice messages now permits ReplyPath presenceAdded explicit rejection of unknown records (even odd ones) in final payloadAdded explicit requirement for ReplyPath when an InvoiceRequest is present
79519244by Bastien Teinturier+14−62 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