cargo-deny
Version updated for https://github.com/EmbarkStudios/cargo-deny-action to version v2.0.15.
- This action is used across all versions by 5,728 repositories.
Go to the GitHub Marketplace to find the latest changes.
Action Summary
The cargo-deny GitHub Action automates the process of analyzing and validating dependencies in Rust projects using the cargo-deny tool. It checks for issues such as banned crates, disallowed licenses, and potential advisories in a project’s dependency tree, helping maintain compliance and security. This action streamlines dependency management, ensuring projects adhere to specified standards and policies.
Release notes
Changed
- PR#802 made relative paths passed to
--configbe resolved relative to the current working directory (rather than the resolved manifest path’s directory). - PR#825 updated
gix,reqwest, andtame-indexto newer versions. Thereqwest0.13 changes means it is no longer possible to choose the source of root certificates forgix, so that decision is now left torustls-platform-verifier. Thenative-certsfeature has thus been removed, andcargo-denyno longer defaults to usingwebpki-roots.
Fixed
- PR#802 fixed path handling of paths passed to
--config, resolving #748. - PR#819 added locations to all SARIF results since that’s mandatory for valid SARIF.
- PR#821 fixed compilation on an Alpine host.
Added
- PR#795 added
[bans.allow-workspace]to allow workspace crates while denying all external crates. - PR#800 added
[licenses.include-build]to toggle whether build dependencies are included in the license check. - PR#823 added
[advisories.unused-ignored-advisory]to disable the warning when an advisory is ignored but not encountered in the crate graph. - PR#826 added
[advisories.unsound]to determine which crates can showunsoundadvisories, similarly to theunmaintainedfield. Defaults toworkspacecrates, ignoringunsoundadvisories for transitive dependencies, resolving #824.