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
16913Commits captured
16841AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16841 analyses
Highest risk·RSS
Moderate 62 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(clear_signing): parse arrays of static structs per the ABI spec.

This commit fixes a bug in how Trezor firmware parses Ethereum transaction data for 'clear signing' of complex smart-contract calls. The parser previously misread arrays of simple structs (e.g., lists of token-swap details) because it assu…

Incorrect ABI decoding of arrays of static structs could lead to mis-displayed transaction fields during clear signing.Mis-decoded fields may cause users to approve transactions different from what they see, or trigger blind-signing fallback.Bounds-check improvements and rejection of zero-field tuples reduce denial-of-service / unbounded parse risks.
6cf0c47dby PrisionMike+186−1445 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(deps): bump libusb1 to v3.4.0

This is a routine dependency update. The project upgraded a helper library called libusb1 from version 3.3.1 to 3.4.0 to silence warnings on future Python versions, and removed a temporary rule that had kept an older cryptography package p…

f0db6145by M1nd3r+10−132 files
No security note in commit
Informational 19 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(python): make merkle tree balanced

This commit changes how Trezor's Python library builds Merkle trees so that the trees are balanced. Previously, leftover odd nodes were pushed upward, which could make some membership proofs much longer than others. The change is described…

Merkle tree construction algorithm changed from unbalanced to balancedMembership proof lengths now differ by at most one across all leavesNo vendor security advisory, CVE, or changelog security note present
6c40c944by M1nd3r+47−304 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): make wireless charging driver optional

This commit reorganizes how the wireless charging chip driver is included in the Trezor firmware. Previously, the driver was always compiled in for certain hardware models; now it is an optional feature that is enabled only for boards that…

340dbf7eby tychovrahe+55−199 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Add changelog entry for silentpayments module

This commit only adds a changelog entry describing a new 'silentpayments' feature that was already added to the project. It changes no code, no build files, and no configuration. There is no security issue in this commit itself.

d9ac2ee5by Sebastian Falbesoner+6−01 file
No security note in commit
Informational 15 AI analysisMessage 86 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: API docs and internal comment followups

This commit only updates documentation comments and an example error message in the silent payments module. It does not change any executable code, cryptographic calculations, or security behavior. The changes clarify when the output-creat…

0fa38f3dby Sebastian Falbesoner+24−223 files
No security note in commit
Moderate 57 AI analysisMessage 55 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Preserve hardened firmware verification result

This bootloader patch changes how the result of a security check on the currently-running firmware is stored. Previously, the code immediately converted the secure verification result into a plain true/false boolean. Now it keeps the speci…

Hardened firmware verification result preservationReplacement of bool with secresult for security-critical return valueBootloader update path depends on firmware validity check
a6efb276by Jack+5−51 file
Vendor flagged security relevance
Low 36 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(common,core,python,tests): add support for StellarInvokeHostFunctionOp.

This commit adds support for signing Stellar Soroban smart-contract transactions on Trezor hardware wallets. It introduces new message types, on-device confirmation screens, and serialization logic for complex contract arguments and author…

New signing path for smart-contract operations with large, nested, user-supplied data structuresUI formatting logic explicitly tries to prevent delimiter forgery in displayed SCV_STRING/SYMBOL valuesAuthorization entries with ADDRESS credentials are not shown by default; user must opt in
05344ecdby Jun Luo+8918−123343 files
No security note in commit
Moderate 59 AI analysisMessage 35 · Opaque
FD FoundationPassport firmware BitcoinHardware wallets

Harden firmware update validation

This commit changes how Passport's bootloader checks firmware updates. Previously, if the currently-running firmware failed validation, the bootloader would skip verifying the new update's signature and could install it anyway. Now the new…

Bypassed/missing cryptographic verification path hardenedFirmware update signature check moved to unconditional executionCurrent firmware invalid state no longer skips new firmware signature verification
b157473cby Jack+30−261 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 81 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

qt: rename color themes (the user-visible names of the themes)

This commit simply renames two color theme labels shown in Electrum's settings window. 'Light' is renamed to 'System' and 'Dark' is renamed to 'qdarkstyle' to better describe what each option actually does. There are no code logic changes,…

1408d6d4by SomberNight+2−21 file
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