Download stats

Nobody has claimed this yet.

What about including download stats as a parameter correlating to usage of a given module?

The raw data for `node-modules` package: http://isaacs.iriscouch.com/downloads/_design/app/_view/pkg?group_level=2&start_key=%5B%22node-modules%22%5D&end_key=%5B%22node-modules%22%2C%7B%7D%5D

Getting the data using `request` library:

``` javascript
request('http://isaacs.iriscouch.com/downloads/_design/app/_view/pkg', {
json: true,
qs: {
group_level: '2',
start_key: JSON.stringify([name]),
end_key: JSON.stringify([name, {}])
}
}, function(error, response, body) {
// ...
});
```

The stats should be aggregated (per week, per month, per year).

Start by inspecting the repository's existing module-search entry point to determine where a download-stats parameter could be exposed. Review the supplied CouchDB view URL and request example, then define the weekly, monthly, and yearly aggregation output; the work is done when those periods are available as documented stats.

Written by the indexing model from the issue text.