@bburns632 @jayqi it's been a bit over a year since we did a release to CRAN. Want to do one?

I found myself using {pkgnet} this week to prep for a talk, and I really wanted the features from uptake/pkgnet#243, which I realize now never made it to CRAN.

If you're open to spending a little time on {pkgnet}, I'd also be happy to submit PRs for the warnings on https

As evident in the screenshot, lodash 4.7.11 is recommended as the fix version for a vulnerability. However, subsequently the same version is flagged as vulnerable with 4.7.12 as the fix version. Suggest mode exists to resolve this type of issues.

Suggest mode is only gett

In some cases, we assume the name of a library/application is the name of the repository in which the file resides. This works for many projects where you might use a repository per library or application but doesn't work as well for mono-repositories where files may be scattered across subdirectories. One simple way to handle this would be to pass along the file path in addition to the URL to the

Currently, the details endpoint displays raw JSON data. It should display that data in a more user-friendly manner.

There is no current requirement for technology to be used here, and for the data itself, it only needs to be the same that is currently provided.