One problem with the AGPL is that it seems to work for projects that are totally owned by one individual or company because there is a clear stratgey for supporting alternative commercial use licenses with no software distribution requirements. If alternative use licenses are low cost for received value and if the commercial license passes corporate lawyer scrutiny, all is good.
The big problem with the AGPL is projects with multiple contributers - makes a paid for commercial license difficult.
The patent / IP language in the GPLv3 still scares a lot of larger companies, my employer included. It's in Blackduck's commercial interest to present information in a way that exaggerates the prominence of that family of licenses. Thus, the chart is of the number of projects released under that license, and does not take into account the maturity or market penetration of a project. For instance, a new entry on Sourceforge with nothing but a README in its repo would be included in Blackduck's count.
That's not to say Blackduck itself is all bad, mind you. I've sat through a few Continuing Legal Education webinars that they've hosted, and they've all been quite objective and accurate. In each case, they brought in fairly prominent figures from the Open Source law space (Karen Copenhaver, Mark Radcliffe, etc) for the sessions.