Future: Consider adding bug report processing information

[david-a-wheeler]

Consider the following (from the paper section 5.B):
Gather and analyze bug report processing (e.g., how long (on average) does it take to respond to a bug report, and how many bug reports lie unresolved after some time (such as 90 days)). This turns out to be hard data to gather across a large number of projects, because many projects do not separate bug reports from enhancement requests. The “isitmaintained.com” site can analyze GitHub projects to separate bug reports from enhancement requests, but it cannot analyze projects on sites other than
GitHub, and it requires that a project use one of the tags it knows about.

[vrisk]

How about you use the time to address Coverity bugs as a proxy for the reactivity to bug reports? Almost all of the projects you are looking at will be set up for regular scans, and that information should be easier to get.