We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.
AI analysis is published as generated. Community notes appear after human validation.
This commit is a routine code reorganization: it moves the WitnessProgram type and its error handling from the main bitcoin crate into a new bitcoin-addresses sub-crate, then re-exports it so existing users still see the same public API. T…
3716268bby Mitchell Bagot+258−2368 filesThis commit tightens how the Keystone hardware wallet's fingerprint sensor driver checks incoming data lengths. Before the change, the code could be tricked into reading or writing past the end of a fixed-size buffer if a malformed fingerp…
7d5f456bby aaron+16−31 fileThis commit simply adds the secure-element generation number (for example, a chip revision identifier) next to the firmware version string on three user-interface screens: the About page, the device-info page, and the welcome/setup page. I…
36e1d3a6by aaron+15−73 filesThis commit only adds two new test cases to a JSON test file used by Bitcoin Core's automated test suite. The tests verify that certain script operations (CHECKSIGVERIFY and CHECKMULTISIGVERIFY) produce the expected error codes when they f…
a86a96d1by azuchi+4−01 fileThis commit only updates a documentation file that shows the project's internal dependency tree. No program code was changed, so it cannot introduce or fix a security vulnerability on its own.
3ee5556fby Tobin C. Harding+420−1501 fileThis commit only edits a changelog file, adding hyperlinks to previously merged pull requests and fixing a minor formatting bullet point. It does not change any source code, build scripts, tests, or documentation that affects how the softw…
2b815008by Tobin C. Harding+5−11 fileThis is a routine subtree update that pulls in a new version of the libmultiprocess IPC helper library used by Bitcoin Core. The changes include bug fixes, new features (thread pools, unordered_set support, optional primitive fields), and …
6b0a9073by Ryan Ofsky+658−33225 filesThis commit changes a CI workflow for the rust-lightning project. It stops trying to push new fuzz test inputs directly to a corpus repository from automated test runs, and instead uploads them as a temporary artifact that a separate sched…
b9f55b6cby Matt Corallo+52−451 fileThis commit only adds a new regression test. It does not change any production code. The test verifies that modern LDK can still read and write very old (pre-0.1) channel monitor update records that used a special sentinel value (u64::MAX)…
19741bf2by GideonBature+91−01 fileThis is a routine code-maintenance change: the developers are marking an old helper macro as deprecated and telling users how to write the same code by hand. There is no bug fix, no security patch, and no vulnerability being addressed in t…
ac921e97by jrakibi+26−123 filesThis commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and line breaks in five files. There are no functional changes, no bug fixes, and no security-related modifications.
673e5ee4by Fmt Bot+12−115 filesThis commit tightens the Android build process for the Electrum Bitcoin wallet. It stops an automated build tool (buildozer) from silently downloading unversioned Python helper packages, and instead installs the 'ninja' build tool from the…
b0701e9dby SomberNight+11−53 filesA 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.