Built by Andrew Edmond · technical diligence across dozens of Amazon deals · CTO, Woot.com
Technical due diligence, read from the repository itself.
History and working tree, rated on the dimensions a deal team cares about. What the code cannot answer becomes a question for the room.
The commit, path and lines it rests on, or, when something is missing, what was looked for.
Public repos need no access at all. For private ones, the collector reads it there. What it sends: never whole files; facts and short excerpts of up to 120 characters where a check matched.
Sell side
In a real process, an investment bank puts someone like me in front of your engineering team weeks before anyone else sees the code. Every problem found then is a problem you still have time to fix. Found later, it is a discount.
Buy side
Your diligence team has a fixed number of hours and more targets than hours. A repo survey is a cheap first read — enough to tell which targets deserve the expensive attention, and which questions to open with when they get it.