If the code could track backwards (skipping merge commits) and figure out who's to blame for the outdated commits, it could include a blame field of some sort that would allow a consumer to do something more intelligent (eg, email the correct person to blame) with the results.
If the code could track backwards (skipping merge commits) and figure out who's to blame for the outdated commits, it could include a blame field of some sort that would allow a consumer to do something more intelligent (eg, email the correct person to blame) with the results.