Currently, the various ospo actions are completely independent. But users who adopt several of them end up restating a lot of configuration for them which would ideally be centralized. As concrete examples, setting:

• a list of repositories to ignore from reporting, or conversely a list of ones to only report
• whether to execute in dry run mode or not
• output formats / destinations that are not the default
• ... probably others ...

would be better served by a common configuration file that all of the actions know to look for.