NsDepCop is a static code analysis tool that helps to enforce namespace dependency rules in C# projects. No more unplanned or unnoticed dependencies in your system.
@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.
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
Basic Primitives Diagrams for JavaScript - data visualization components library that implements organizational chart and multi-parent dependency diagrams, contains implementations of JavaScript Controls and PDF rendering plugins.
Some testing suggests that deps.rs supports projects hosted on github and gitlab but not my project's which are on sourcehut. At least, when specifying a repository path such as https://deps.rs/repo/sourcehut/~tsdh/swayr or https://deps.rs/repo/srht/~tsdh/swayr, I get the error "Could not parse repository path".
The actual repository is https://git.sr.ht/~tsdh/swayr.