It's not the fact that there is server-side code integration included.  It's because their specific implementation in their themes wasn't passing basic security standards/scans.   

If you really want action at this point for this specific issue, I'd suggest e-mailing Ash since he's not participating in this thread any longer.  You should even CC the folks at DNNGo on the same e-mail if you want to really see what the remaining issues are.  From what I've been told, there have been things reported that aren't entirely accurate.

ash.prasad@dnnsoftware.com

This already exists (link below), but I don't believe this is the sole responsibility of DNN Corp. This is a responsibility for all of us. We're an open source project - now more than ever before. 

http://www.dnnsoftware.com/wiki/secur...

I agree that DNN Corp should tell developers what fails a security audit when it's necessary to remove product(s) from the DNN Store, and that's what has happened in this case.  Beyond the wiki article I've posted, any developer simply needs to observe the commonly accepted security best practices that can be found with any Google search.  

This isn't DNN Corp creating arbitrary standards, and publishing security standards really isn't their responsibility either - nor would it be for any other vendor.  Their responsibility is simply to protect customers that pay money on the store.