This is not currently in our plan to allow our users to compare two environments.
We might do it in the future, possibly starting with permission as it seems like it would be the most useful part on security level.
We’ve release a version of Workflow reporting a few months ago and are trying to figure out where we are going with this.
Please tell us what you would like us to add to this feature.
An error occurred while saving the commentMats Hindhede commented
By far the most important thing to report on workflows is their name and location, of course. You need a proper list with the name and location of each workflow in the web app or site collection. This is an obvious need and SharePoint OOTB doesn't help you one bit with that. It's also surprisingly hard to script, since 2010 and 2013 WFs are handled differently. A script that lists 2013 WFs and their locations is quite different from a script that lists 2010 WFs, and also more complicated. Of course, you don't care if they are 2013 or 2010 WFs, that's just MS messing things up. You just want to know where the heck your workflows are, especially if there are hundreds or thousands. Apart from name and location, it would also be nice to know if the workflows are OOTB, SPD, 2010, 2013 or Nintex and who created them, how many running instances they currently have, how they are triggered etc.