fork/wezterm
git clone https://git.julia.blue/fork/wezterm
14d426fea
termwiz-0.23.2
1# This template contains all of the possible sections and their default values 2 3# Note that all fields that take a lint level have these possible values: 4# * deny - An error will be produced and the check will fail 5# * warn - A warning will be produced, but the check will not fail 6# * allow - No warning or error will be produced, though in some cases a note 7# will be 8 9# The values provided in this template are the default values that will be used 10# when any section or field is not specified in your own configuration 11 12# Root options 13 14# The graph table configures how the dependency graph is constructed and thus 15# which crates the checks are performed against 16[ graph ] 17# If 1 or more target triples (and optionally, target_features) are specified, 18# only the specified targets will be checked when running `cargo deny check`. 19# This means, if a particular package is only ever used as a target specific 20# dependency, such as, for example, the `nix` crate only being used via the 21# `target_family = "unix"` configuration, that only having windows targets in 22# this list would mean the nix crate, as well as any of its exclusive 23# dependencies not shared by any other crates, would be ignored, as the target 24# list here is effectively saying which targets you are building for. 25targets = [ 26# The triple can be any string, but only the target triples built in to 27# rustc (as of 1.40) can be checked against actual config expressions 28#"x86_64-unknown-linux-musl", 29# You can also specify which target_features you promise are enabled for a 30# particular target. target_features are currently not validated against 31# the actual valid features supported by the target architecture. 32#{ triple = "wasm32-unknown-unknown", features = ["atomics"] }, 33] 34# When creating the dependency graph used as the source of truth when checks are 35# executed, this field can be used to prune crates from the graph, removing them 36# from the view of cargo-deny. This is an extremely heavy hammer, as if a crate 37# is pruned from the graph, all of its dependencies will also be pruned unless 38# they are connected to another crate in the graph that hasn't been pruned, 39# so it should be used with care. The identifiers are [Package ID Specifications] 40# (https://doc.rust-lang.org/cargo/reference/pkgid-spec.html) 41#exclude = [] 42# If true, metadata will be collected with `--all-features`. Note that this can't 43# be toggled off if true, if you want to conditionally enable `--all-features` it 44# is recommended to pass `--all-features` on the cmd line instead 45all-features = false 46# If true, metadata will be collected with `--no-default-features`. The same 47# caveat with `all-features` applies 48no-default-features = false 49# If set, these feature will be enabled when collecting metadata. If `--features` 50# is specified on the cmd line they will take precedence over this option. 51#features = [] 52 53# The output table provides options for how/if diagnostics are outputted 54[ output ] 55# When outputting inclusion graphs in diagnostics that include features, this 56# option can be used to specify the depth at which feature edges will be added. 57# This option is included since the graphs can be quite large and the addition 58# of features from the crate(s) to all of the graph roots can be far too verbose. 59# This option can be overridden via `--feature-depth` on the cmd line 60feature-depth = 1 61 62# This section is considered when running `cargo deny check advisories` 63# More documentation for the advisories section can be found here: 64# https://embarkstudios.github.io/cargo-deny/checks/advisories/cfg.html 65[ advisories ] 66# The path where the advisory databases are cloned/fetched into 67#db-path = "$CARGO_HOME/advisory-dbs" 68# The url(s) of the advisory databases to use 69#db-urls = ["https://github.com/rustsec/advisory-db"] 70# A list of advisory IDs to ignore. Note that ignored advisories will still 71# output a note when they are encountered. 72ignore = [ 73#"RUSTSEC-0000-0000", 74#{ id = "RUSTSEC-0000-0000", reason = "you can specify a reason the advisory is ignored" }, 75#"a-crate-that-is-yanked@0.1.1", # you can also ignore yanked crate versions if you wish 76#{ crate = "a-crate-that-is-yanked@0.1.1", reason = "you can specify why you are ignoring the yanked crate" }, 77] 78# If this is true, then cargo deny will use the git executable to fetch advisory database. 79# If this is false, then it uses a built-in git library. 80# Setting this to true can be helpful if you have special authentication requirements that cargo-deny does not support. 81# See Git Authentication for more information about setting up git authentication. 82#git-fetch-with-cli = true 83 84# This section is considered when running `cargo deny check licenses` 85# More documentation for the licenses section can be found here: 86# https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html 87[ licenses ] 88# List of explicitly allowed licenses 89# See https://spdx.org/licenses/ for list of possible licenses 90# [possible values: any SPDX 3.11 short identifier (+ optional exception)]. 91allow = [ 92"MIT" , 93"Apache-2.0" , 94"LGPL-2.1" , 95"Unicode-DFS-2016" , 96"Zlib" , 97"BSD-2-Clause" , 98"BSD-3-Clause" , 99"MPL-2.0" , 100"ISC" , 101"CC0-1.0" , 102"WTFPL" , 103"Apache-2.0 WITH LLVM-exception" , 104"OpenSSL" , 105] 106# The confidence threshold for detecting a license from license text. 107# The higher the value, the more closely the license text must be to the 108# canonical license text of a valid SPDX license file. 109# [possible values: any between 0.0 and 1.0]. 110confidence-threshold = 0.8 111# Allow 1 or more licenses on a per-crate basis, so that particular licenses 112# aren't accepted for every possible crate as with the normal allow list 113exceptions = [ 114# Each entry is the crate and version constraint, and its specific allow 115# list 116#{ allow = ["Zlib"], crate = "adler32" }, 117] 118 119# Some crates don't have (easily) machine readable licensing information, 120# adding a clarification entry for it allows you to manually specify the 121# licensing information 122[[ licenses . clarify ]] 123# The package spec the clarification applies to 124crate = "ring" 125# The SPDX expression for the license requirements of the crate 126expression = "MIT AND ISC AND OpenSSL" 127# One or more files in the crate's source used as the "source of truth" for 128# the license expression. If the contents match, the clarification will be used 129# when running the license check, otherwise the clarification will be ignored 130# and the crate will be checked normally, which may produce warnings or errors 131# depending on the rest of your configuration 132license-files = [ 133# Each entry is a crate relative path, and the (opaque) hash of its contents 134{ path = "LICENSE" , hash = 0xbd0eed23 } 135] 136 137[ licenses . private ] 138# If true, ignores workspace crates that aren't published, or are only 139# published to private registries. 140# To see how to mark a crate as unpublished (to the official registry), 141# visit https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field. 142ignore = true 143# One or more private registries that you might publish crates to, if a crate 144# is only published to private registries, and ignore is true, the crate will 145# not have its license(s) checked 146registries = [ 147#"https://sekretz.com/registry 148] 149 150# This section is considered when running `cargo deny check bans`. 151# More documentation about the 'bans' section can be found here: 152# https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html 153[ bans ] 154# Lint level for when multiple versions of the same crate are detected 155multiple-versions = "warn" 156# Lint level for when a crate version requirement is `*` 157wildcards = "allow" 158# The graph highlighting used when creating dotgraphs for crates 159# with multiple versions 160# * lowest-version - The path to the lowest versioned duplicate is highlighted 161# * simplest-path - The path to the version with the fewest edges is highlighted 162# * all - Both lowest-version and simplest-path are used 163highlight = "all" 164# The default lint level for `default` features for crates that are members of 165# the workspace that is being checked. This can be overridden by allowing/denying 166# `default` on a crate-by-crate basis if desired. 167workspace-default-features = "allow" 168# The default lint level for `default` features for external crates that are not 169# members of the workspace. This can be overridden by allowing/denying `default` 170# on a crate-by-crate basis if desired. 171external-default-features = "allow" 172# List of crates that are allowed. Use with care! 173allow = [ 174#"ansi_term@0.11.0", 175#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is allowed" }, 176] 177# List of crates to deny 178deny = [ 179#"ansi_term@0.11.0", 180#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is banned" }, 181# Wrapper crates can optionally be specified to allow the crate when it 182# is a direct dependency of the otherwise banned crate 183#{ crate = "ansi_term@0.11.0", wrappers = ["this-crate-directly-depends-on-ansi_term"] }, 184] 185 186# List of features to allow/deny 187# Each entry the name of a crate and a version range. If version is 188# not specified, all versions will be matched. 189#[[bans.features]] 190#crate = "reqwest" 191# Features to not allow 192#deny = ["json"] 193# Features to allow 194#allow = [ 195# "rustls", 196# "__rustls", 197# "__tls", 198# "hyper-rustls", 199# "rustls", 200# "rustls-pemfile", 201# "rustls-tls-webpki-roots", 202# "tokio-rustls", 203# "webpki-roots", 204#] 205# If true, the allowed features must exactly match the enabled feature set. If 206# this is set there is no point setting `deny` 207#exact = true 208 209# Certain crates/versions that will be skipped when doing duplicate detection. 210skip = [ 211#"ansi_term@0.11.0", 212#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason why it can't be updated/removed" }, 213] 214# Similarly to `skip` allows you to skip certain crates during duplicate 215# detection. Unlike skip, it also includes the entire tree of transitive 216# dependencies starting at the specified crate, up to a certain depth, which is 217# by default infinite. 218skip-tree = [ 219#"ansi_term@0.11.0", # will be skipped along with _all_ of its direct and transitive dependencies 220#{ crate = "ansi_term@0.11.0", depth = 20 }, 221] 222 223# This section is considered when running `cargo deny check sources`. 224# More documentation about the 'sources' section can be found here: 225# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.html 226[ sources ] 227# Lint level for what to happen when a crate from a crate registry that is not 228# in the allow list is encountered 229unknown-registry = "warn" 230# Lint level for what to happen when a crate from a git repository that is not 231# in the allow list is encountered 232unknown-git = "warn" 233# List of URLs for allowed crate registries. Defaults to the crates.io index 234# if not specified. If it is specified but empty, no registries are allowed. 235allow-registry = [ "https://github.com/rust-lang/crates.io-index" ] 236# List of URLs for allowed Git repositories 237allow-git = [] 238 239[ sources . allow-org ] 240# 1 or more github.com organizations to allow git sources for 241github = [ "" ] 242# 1 or more gitlab.com organizations to allow git sources for 243gitlab = [ "" ] 244# 1 or more bitbucket.org organizations to allow git sources for 245bitbucket = [ "" ]