dependency-graph

Is your feature request related to a problem? Please describe.
If some package is restricted to use, there is should be a possibility to specify some analogs

Describe the solution you'd like
Add analog and description fields to package target

{
  'restricted-packages': ['error', [{ 
    name: 'foo', 
    description: 'This package has a vulnerability',
    analogs: ['b

It might be helpful to inform people in the guide some hints on setting up private repos such as github using the docker container.

git config --global url."https://$GITHUB_USERNAME:$GITHUB_PASSWORD@github.com".insteadOf /"https://github.com"
ls -l ~/.gitconfig

docker run -e -v $(pwd):/project \
	   -v ~/.gitconfig:/root/.gitconfig \
            ort:latest --info an

Right now argument validation and actually calling the subcommands is lumped together in one function:

https://github.com/rust-secure-code/cargo-supply-chain/blob/776ab090333f4f07a61fe0e66386e49bae5eff45/src/main.rs#L65-L67

This makes them impossible to unit-test and necessitates manual calls to eprintln_help() in multiple places instead of just one in main on any validation error.

We

@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