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 simply renames a GitHub Actions workflow file and changes its schedule from weekly to monthly. It is a routine CI maintenance change with no security relevance.
778018e1by Nick Johnson+46−461 fileThis commit seals a small helper trait called WorkExt so that outside users of the library can no longer implement it themselves. Before the change, enabling the optional `std` feature silently added a new method (log2) to the trait withou…
73efa990by Nick Johnson+2−11 fileThis commit is a simple housekeeping change for the project's fuzz-testing scripts. It removes a small helper file (fuzz-util.sh) and copies its functions directly into another script (generate-bins.sh). There is no change to the actual Bi…
b41211deby Nick Johnson+21−482 filesThis commit is a routine cleanup of the project's fuzz-testing shell scripts. It merges the old cycle.sh script into fuzz.sh and adds a -cycle command-line flag. There is no change to the actual Bitcoin library code, no bug fix, and no sec…
a673433bby Nick Johnson+64−493 filesThis commit refactors a fuzz-testing shell script to stop using a local helper file and instead use the standard 'cargo-fuzz' tool directly. It is a build/test tooling change with no apparent effect on the security of the actual Bitcoin li…
351903c5by Nick Johnson+7−231 fileThis is a small fix inside a test file for the silent payments module. It makes sure a function that converts a public key into bytes actually succeeds before comparing those bytes against expected test values. Previously, the test could c…
93280c22by Lőrinc+1−11 fileThis commit fixes two test cases in the secp256k1 cryptographic library so they now verify that a public-key sorting function actually succeeds before checking its output. Previously the tests only inspected the sorted result and ignored w…
a2ad68cdby Lőrinc+2−21 fileThis commit tightens a test suite for the secp256k1 cryptographic library. It adds checks to ensure that recoverable signing and signature conversion succeed before using their outputs. It does not change the library's actual signing or ve…
1d3f72d3by Lőrinc+3−31 fileThis change is inside the library's test code, not the actual cryptographic code used by applications. It makes two test setup steps verify they succeeded before using their results. Previously the test could have continued with invalid da…
0618af81by Lőrinc+2−21 fileThis change fixes a small but real flaw in the MuSig test code. Previously, two test helper functions called internal loading/summing routines and then checked whether the results were the special 'point at infinity' value. Because the inp…
b8de1bc3by Lőrinc+2−21 fileThis commit fixes test code for the EllSwift module so that it actually checks whether encoding, decoding, and public-key loading operations succeed before using their outputs. Previously the tests silently ignored failure return values, w…
564afb0bby Lőrinc+10−102 filesThis is a one-line change to a test file in the secp256k1 cryptographic library. It makes an existing exhaustive test stricter by requiring a function to report success before checking its output. It does not change any production code and…
658c7edcby Lőrinc+1−11 fileA 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.