It's presented as an article about a problem that OSS has. "Oh, and by the way here's a product that happens to target that problem, and while it's not perfect it's better than nothing."

I think the danger or a product like this, and particularly this type of article pimping it, is it becomes fodder for people to argue against OSS: "See, if you start using OSS you'll have to invest in the additional products and processes, and even then it might not work."

No one with a vested interest in selling this product, nor in making this argument, will ever concede that the only reason you don't do this with closed source programs is that you have no code to compare against.

So you solve the problem of unknowingly including OSS code in your product by purchasing this tool and auditing everything. You solve the problem of unknowingly including closed code in your product by not looking for it, and hoping no one else can look at your code either.