The runs endpoint should also provide information about the user who triggered a run

[sschuberth]

Runs can usually be triggered by different users of the organization. Esp. during technical on-boarding of projects, user might need to experiment with different analyzer options, and trigger different runs for them In order to trace the last run of a specific user, the name of the user who triggered a runs should be part of the details returned for a run in order to display the user in the front-end as part of the runs table.