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

Changes worth understanding

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

17152 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

Fix repo renamings for Ledger apps

This commit simply updates web links and folder names in HWI's build scripts and documentation to match Ledger's renamed GitHub repositories. It does not change any wallet code, cryptography, or user-facing behavior. There is no security i…

f15d6d9aby Salvatore Ingala+8−83 files
No security note in commit
Low 47 AI analysisMessage 45 · Thin
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

psbt: enforce required locktime bounds

This change makes the hardware-wallet interface library stricter when reading PSBT (Partially Signed Bitcoin Transaction) files. It now rejects locktime values that don't follow Bitcoin's rules: a time-based locktime must be at least 500,0…

Input validation added to PSBT deserializationEnforcement of Bitcoin locktime semantics boundary (500000000)New negative test cases for invalid locktime combinations
498e85a7by Sjors Provoost+8−12 files
No security note in commit
Moderate 63 AI analysisMessage 65 · Adequate
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

psbt: reject PSBTv2 input and output fields in PSBTv0

This commit fixes a parsing bug in the way the Hardware Wallet Interface (HWI) reads Bitcoin transaction files called PSBTs. PSBTs come in two versions, v0 and v2, and each version has its own allowed fields. The code was accidentally acce…

PSBT version confusion: v2-only fields accepted in v0 PSBTPotential transaction malleability / unintended signature scopeParsing strictness fix with new negative test vectors
2a431b88by Sjors Provoost+22−42 files
No security note in commit
Low 46 AI analysisMessage 60 · Adequate
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

psbt: track whether an unsigned tx key was seen

This change fixes a subtle parsing bug in how the wallet software reads PSBT (Partially Signed Bitcoin Transaction) files. Previously, the code could not tell the difference between a PSBT that genuinely contained an unsigned transaction w…

Ambiguous sentinel value used as a proxy for key presencePSBT version-specific validation bypass possibleNew test vector added for empty unsigned transaction edge case
8a405230by Sjors Provoost+6−32 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

psbt: parse the global unsigned tx without witness data

This commit fixes a bug in how the wallet interface reads the unsigned transaction embedded inside a PSBT (Partially Signed Bitcoin Transaction). Previously, the parser tried to auto-detect whether the transaction included witness data, wh…

PSBT global unsigned transaction parsing now strictly enforces non-witness serializationNew deserialize_without_witness method removes witness-marker auto-detectionAdds explicit PSBTSerializationError for invalid or trailing bytes in the unsigned tx field
b34f94a6by Sjors Provoost+19−33 files
No security note in commit
Informational 12 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

releases: add v9.26.2, v9.26.3 and v9.26.4

This commit is a routine release-management update. It adds signed build assertions for three new BitBox02 firmware versions (9.26.2, 9.26.3, 9.26.4) and updates the release documentation and build helper script. The build script now delet…

No firmware source code is modifiedNo cryptographic primitives or protocols are changedNo bug fixes or vulnerability mitigations are present in the diff
eed2e68eby Marko Bencun+79−116 files
No security note in commit
Informational 15 AI analysisMessage 88 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: Remove incorrect code comment

This commit only deletes an incorrect explanatory comment. The actual code behavior does not change at all. It is a documentation cleanup, not a security fix.

980ccfd5by Tobin C. Harding+1−61 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Format Zcash PCZT code

This commit only reformats existing Zcash PCZT code—adjusting line breaks, indentation, and whitespace. No logic, behavior, or security checks were changed.

a759792cby Adam Tucker+26−233 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Remove myself as security contact

This commit simply removes one person (Pieter Wuille) from the list of security contacts in the project's SECURITY.md file. It is an administrative change to the documented contact list and does not alter any code, fix any bug, or change a…

629df81eby Pieter Wuille+0−11 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: enable pyright for emu.py and scripts in test/

This commit is a routine developer tooling change. It turns on stricter Python type checking (Pyright) for the emulator script and some test helper scripts, and makes small code adjustments so those files pass the new checks. There is no c…

16a7a0b8by Martin Milata+34−259 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): enable logging from tests and fixtures

This commit only changes test infrastructure. It enables extra logging output during automated testing so developers can see more detail when running tests. There is no change to the actual Trezor firmware or wallet security code, and no s…

a22031d5by Martin Milata+7−01 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