You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to start using cargo-deny for only one feature: catching accidental uses of an unwanted crate. However, it seems that the functionality of cargo-deny is all-or-nothing, and set to very strict requirements, which makes it difficult and laborious to adopt.
I could not find a way to disable checking of rustsec advisories, and I couldn't find a way to downgrade "unmaintained" advisories to a warning. To me these advisories are not urgent, and don't justify stopping CI jobs for. I don't see a way to use cargo-deny without it failing checks, and requiring immediate action whenever some dependency gets marked as unmaintained.
I also couldn't find a way to either disable or easily set up checking of licenses. The cargo deny init command doesn't populate licenses.allow with the currently used licenses. I don't see any shortcut to allow all standard "permissive" licenses, so the setup requires copy'n'pasting a bunch of license names.
The internal projects I work on have private git dependencies with missing license information (license = ""), and cargo-deny doesn't like that. I don't see a good option to deal with this. There's licenses.private.registries (not working?), but there isn't a similar list for git repos. license.clarfiy needs to be set per crate, and requires an SPDX expression, which doesn't allow proprietary private-use-only licenses.
The text was updated successfully, but these errors were encountered:
A config option would be useful, because other collaborators wouldn't need to be instructed to run with specific args, and wonder why the checks are failing in the default configuration.
I wanted to start using cargo-deny for only one feature: catching accidental uses of an unwanted crate. However, it seems that the functionality of cargo-deny is all-or-nothing, and set to very strict requirements, which makes it difficult and laborious to adopt.
I could not find a way to disable checking of rustsec advisories, and I couldn't find a way to downgrade "unmaintained" advisories to a warning. To me these advisories are not urgent, and don't justify stopping CI jobs for. I don't see a way to use
cargo-deny
without it failing checks, and requiring immediate action whenever some dependency gets marked as unmaintained.I also couldn't find a way to either disable or easily set up checking of licenses. The
cargo deny init
command doesn't populatelicenses.allow
with the currently used licenses. I don't see any shortcut to allow all standard "permissive" licenses, so the setup requires copy'n'pasting a bunch of license names.The internal projects I work on have private git dependencies with missing license information (
license = ""
), andcargo-deny
doesn't like that. I don't see a good option to deal with this. There'slicenses.private.registries
(not working?), but there isn't a similar list for git repos.license.clarfiy
needs to be set per crate, and requires an SPDX expression, which doesn't allow proprietary private-use-only licenses.The text was updated successfully, but these errors were encountered: