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
Currently as we use cargo_metadata crate the user running cargo-deny also have to have the full Cargo toolchain installed, in other words: cargo-deny is not a fully standalone executable.
This is ok and good for the default use case as it is very likely a user that is interested in using cargo-deny also have Cargo and Rust installed :)
But for CI and/or minimal docker images it would be nice if we had an optional feature flag for using the cargo crate and output_metadata directly on it instead of invoking cargo.exe. Can still take the .json output and feed it into cargo_metadata to leave the rest of the code and parsing unchanged.
The text was updated successfully, but these errors were encountered:
Currently as we use
cargo_metadata
crate the user runningcargo-deny
also have to have the full Cargo toolchain installed, in other words:cargo-deny
is not a fully standalone executable.This is ok and good for the default use case as it is very likely a user that is interested in using
cargo-deny
also have Cargo and Rust installed :)But for CI and/or minimal docker images it would be nice if we had an optional feature flag for using the
cargo
crate andoutput_metadata
directly on it instead of invokingcargo.exe
. Can still take the .json output and feed it intocargo_metadata
to leave the rest of the code and parsing unchanged.The text was updated successfully, but these errors were encountered: