fork/cargo

git clone https://git.julia.blue/fork/cargo

Ed PageUpdate all dependencies (#15166)39399182a

0.93.0
10.9 KiB243 linesraw
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"]
70yanked = "warn"
71# A list of advisory IDs to ignore. Note that ignored advisories will still
72# output a note when they are encountered.
73ignore = [
74    #"RUSTSEC-0000-0000",
75    #{ id = "RUSTSEC-0000-0000", reason = "you can specify a reason the advisory is ignored" },
76    #"a-crate-that-is-yanked@0.1.1", # you can also ignore yanked crate versions if you wish
77    #{ crate = "a-crate-that-is-yanked@0.1.1", reason = "you can specify why you are ignoring the yanked crate" },
78]
79# If this is true, then cargo deny will use the git executable to fetch advisory database.
80# If this is false, then it uses a built-in git library.
81# Setting this to true can be helpful if you have special authentication requirements that cargo-deny does not support.
82# See Git Authentication for more information about setting up git authentication.
83#git-fetch-with-cli = true
84
85# This section is considered when running `cargo deny check licenses`
86# More documentation for the licenses section can be found here:
87# https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html
88[licenses]
89# List of explicitly allowed licenses
90# See https://spdx.org/licenses/ for list of possible licenses
91# [possible values: any SPDX 3.11 short identifier (+ optional exception)].
92allow = [
93    "MIT",
94    "MIT-0",
95    "Apache-2.0",
96    "BSD-2-Clause",
97    "BSD-3-Clause",
98    "MPL-2.0",
99    "Unicode-3.0",
100    "CC0-1.0",
101    "ISC",
102    "Zlib",
103]
104# The confidence threshold for detecting a license from license text.
105# The higher the value, the more closely the license text must be to the
106# canonical license text of a valid SPDX license file.
107# [possible values: any between 0.0 and 1.0].
108confidence-threshold = 0.8
109# Allow 1 or more licenses on a per-crate basis, so that particular licenses
110# aren't accepted for every possible crate as with the normal allow list
111exceptions = [
112    # Each entry is the crate and version constraint, and its specific allow
113    # list
114    #{ allow = ["Zlib"], crate = "adler32" },
115]
116
117# Some crates don't have (easily) machine readable licensing information,
118# adding a clarification entry for it allows you to manually specify the
119# licensing information
120#[[licenses.clarify]]
121# The package spec the clarification applies to
122#crate = "ring"
123# The SPDX expression for the license requirements of the crate
124#expression = "MIT AND ISC AND OpenSSL"
125# One or more files in the crate's source used as the "source of truth" for
126# the license expression. If the contents match, the clarification will be used
127# when running the license check, otherwise the clarification will be ignored
128# and the crate will be checked normally, which may produce warnings or errors
129# depending on the rest of your configuration
130#license-files = [
131# Each entry is a crate relative path, and the (opaque) hash of its contents
132#{ path = "LICENSE", hash = 0xbd0eed23 }
133#]
134
135[licenses.private]
136# If true, ignores workspace crates that aren't published, or are only
137# published to private registries.
138# To see how to mark a crate as unpublished (to the official registry),
139# visit https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field.
140ignore = false
141# One or more private registries that you might publish crates to, if a crate
142# is only published to private registries, and ignore is true, the crate will
143# not have its license(s) checked
144registries = [
145    #"https://sekretz.com/registry
146]
147
148# This section is considered when running `cargo deny check bans`.
149# More documentation about the 'bans' section can be found here:
150# https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html
151[bans]
152# Lint level for when multiple versions of the same crate are detected
153multiple-versions = "warn"
154# Lint level for when a crate version requirement is `*`
155wildcards = "allow"
156# The graph highlighting used when creating dotgraphs for crates
157# with multiple versions
158# * lowest-version - The path to the lowest versioned duplicate is highlighted
159# * simplest-path - The path to the version with the fewest edges is highlighted
160# * all - Both lowest-version and simplest-path are used
161highlight = "all"
162# The default lint level for `default` features for crates that are members of
163# the workspace that is being checked. This can be overridden by allowing/denying
164# `default` on a crate-by-crate basis if desired.
165workspace-default-features = "allow"
166# The default lint level for `default` features for external crates that are not
167# members of the workspace. This can be overridden by allowing/denying `default`
168# on a crate-by-crate basis if desired.
169external-default-features = "allow"
170# List of crates that are allowed. Use with care!
171allow = [
172    #"ansi_term@0.11.0",
173    #{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is allowed" },
174]
175# List of crates to deny
176deny = [
177    #"ansi_term@0.11.0",
178    #{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is banned" },
179    # Wrapper crates can optionally be specified to allow the crate when it
180    # is a direct dependency of the otherwise banned crate
181    #{ crate = "ansi_term@0.11.0", wrappers = ["this-crate-directly-depends-on-ansi_term"] },
182]
183
184# List of features to allow/deny
185# Each entry the name of a crate and a version range. If version is
186# not specified, all versions will be matched.
187#[[bans.features]]
188#crate = "reqwest"
189# Features to not allow
190#deny = ["json"]
191# Features to allow
192#allow = [
193#    "rustls",
194#    "__rustls",
195#    "__tls",
196#    "hyper-rustls",
197#    "rustls",
198#    "rustls-pemfile",
199#    "rustls-tls-webpki-roots",
200#    "tokio-rustls",
201#    "webpki-roots",
202#]
203# If true, the allowed features must exactly match the enabled feature set. If
204# this is set there is no point setting `deny`
205#exact = true
206
207# Certain crates/versions that will be skipped when doing duplicate detection.
208skip = [
209    #"ansi_term@0.11.0",
210    #{ crate = "ansi_term@0.11.0", reason = "you can specify a reason why it can't be updated/removed" },
211]
212# Similarly to `skip` allows you to skip certain crates during duplicate
213# detection. Unlike skip, it also includes the entire tree of transitive
214# dependencies starting at the specified crate, up to a certain depth, which is
215# by default infinite.
216skip-tree = [
217    #"ansi_term@0.11.0", # will be skipped along with _all_ of its direct and transitive dependencies
218    #{ crate = "ansi_term@0.11.0", depth = 20 },
219]
220
221# This section is considered when running `cargo deny check sources`.
222# More documentation about the 'sources' section can be found here:
223# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.html
224[sources]
225# Lint level for what to happen when a crate from a crate registry that is not
226# in the allow list is encountered
227unknown-registry = "warn"
228# Lint level for what to happen when a crate from a git repository that is not
229# in the allow list is encountered
230unknown-git = "warn"
231# List of URLs for allowed crate registries. Defaults to the crates.io index
232# if not specified. If it is specified but empty, no registries are allowed.
233allow-registry = ["https://github.com/rust-lang/crates.io-index"]
234# List of URLs for allowed Git repositories
235allow-git = []
236
237[sources.allow-org]
238# github.com organizations to allow git sources for
239github = []
240# gitlab.com organizations to allow git sources for
241gitlab = []
242# bitbucket.org organizations to allow git sources for
243bitbucket = []