What the history of a small SaaS told me that the demo never would
This week I read the full code and change history of an open-source SaaS that is also sold as a hosted product, the way I would for someone about to buy it. Four things came out of the history and the licence file, and none of them would show up in a demo or a CIM.
The licence decides what you are buying. The code was under the AGPL, with 87 names in its history and no contributor agreement. A buyer of that business gets the hosted service, the customers and the brand, but not exclusive code, and anyone can run the same product. Ask what the licence is and who holds the copyright before the LOI, not after.
One person carried most of it. In the last twelve months one maintainer made three quarters of the changes, and nothing in the code described how the hosted service is deployed or backed up. If that person is not part of the deal, the know-how leaves at closing.
The fix history read like a security timeline. Six security fixes landed between June and November. One of them closed a path that let a user of one customer's account take an admin session on another customer's account. It was fixed properly, with tests. The question for the seller is how long it was open and what the logs from before the fix show, and only the seller can answer that.
Two parts were past their maker's support, one of them the library the product uses for file storage and email. Nothing was broken, but nothing in those parts will get fixed either.
None of this needs the buyer to read code. It needs someone to read the history and the licence and turn what they find into questions for the seller.