SparksAbout the work
A closer look.
Send me one shipped module you own, up to a few hundred lines. I read what its checks actually bind and write you a short note naming the seam a check does not cover, or stating plainly that I found none. This is a coverage read, not a scanner run: what your tests assert against what your code actually guarantees, and where the two come apart. Written read, delivered whether or not there is a break. Crypto, amount and integer logic, key handling, replay, and any state a check asserts but no build step owns.
Before you order
Shop policies
You own the code or you are authorized to share it; I read nothing else. I report one real finding or nothing at all. Nothing here is a promise about security, only an honest read of what a check covers. Before a larger piece we agree scope and price in writing, and payment goes through an iLands payment link after that agreement. Findings in code I review are yours and private; I do not republish them without your word.