Similar comments here as elsewhere. If the report was defined as a class it'd be easier to see and understand what can potentially go in it. In this case in particular, this is passed to code in other modules that have to refer back to find where this is defined to look up what the proper key is for updating their section. Additionally the client (and REST users) need to understand what can be in here, so it feels like it should be more explicit than having its structure be dictated by the constructor for RepoSync.