fork/eza

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

Christina Sørensenfix(deny): add unicode-3.0 license74ec00cd

main
10.8 KiB250 linesraw
1# SPDX-FileCopyrightText: 2024 Christina Sørensen
2# SPDX-License-Identifier: EUPL-1.2
3[graph]
4# This template contains all of the possible sections and their default values
5
6# Note that all fields that take a lint level have these possible values:
7# * deny - An error will be produced and the check will fail
8# * warn - A warning will be produced, but the check will not fail
9# * allow - No warning or error will be produced, though in some cases a note
10# will be
11
12# The values provided in this template are the default values that will be used
13# when any section or field is not specified in your own configuration
14
15# Root options
16
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  #{ triple = "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 = true
46# If true, metadata will be collected with `--no-default-features`. The same
47# caveat with `all-features` applies
48no-default-features = false
49
50[output]
51# If set, these feature will be enabled when collecting metadata. If `--features`
52# is specified on the cmd line they will take precedence over this option.
53#features = []
54# When outputting inclusion graphs in diagnostics that include features, this
55# option can be used to specify the depth at which feature edges will be added.
56# This option is included since the graphs can be quite large and the addition
57# of features from the crate(s) to all of the graph roots can be far too verbose.
58# This option can be overridden via `--feature-depth` on the cmd line
59feature-depth = 1
60
61# This section is considered when running `cargo deny check advisories`
62# More documentation for the advisories section can be found here:
63# https://embarkstudios.github.io/cargo-deny/checks/advisories/cfg.html
64[advisories]
65version = 2
66# The path where the advisory database is cloned/fetched into
67db-path = "~/.cargo/advisory-db"
68# The url(s) of the advisory databases to use
69db-urls = ["https://github.com/rustsec/advisory-db"]
70# The lint level for crates that have been yanked from their source registry
71yanked = "warn"
72# A list of advisory IDs to ignore. Note that ignored advisories will still
73# output a note when they are encountered.
74ignore = [
75  #"RUSTSEC-0000-0000",
76]
77# Threshold for security vulnerabilities, any vulnerability with a CVSS score
78# lower than the range specified will be ignored. Note that ignored advisories
79# will still output a note when they are encountered.
80# * None - CVSS Score 0.0
81# * Low - CVSS Score 0.1 - 3.9
82# * Medium - CVSS Score 4.0 - 6.9
83# * High - CVSS Score 7.0 - 8.9
84# * Critical - CVSS Score 9.0 - 10.0
85#severity-threshold =
86
87# If this is true, then cargo deny will use the git executable to fetch advisory database.
88# If this is false, then it uses a built-in git library.
89# Setting this to true can be helpful if you have special authentication requirements that cargo-deny does not support.
90# See Git Authentication for more information about setting up git authentication.
91#git-fetch-with-cli = true
92
93# This section is considered when running `cargo deny check licenses`
94# More documentation for the licenses section can be found here:
95# https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html
96[licenses]
97version = 2
98# List of explicitly allowed licenses
99# See https://spdx.org/licenses/ for list of possible licenses
100# [possible values: any SPDX 3.11 short identifier (+ optional exception)].
101allow = [
102  "EUPL-1.2",
103  "MIT",
104  "Unicode-DFS-2016",
105  "Apache-2.0",
106  "MPL-2.0",
107  "Unicode-3.0",
108  #"Apache-2.0 WITH LLVM-exception",
109]
110# The confidence threshold for detecting a license from license text.
111# The higher the value, the more closely the license text must be to the
112# canonical license text of a valid SPDX license file.
113# [possible values: any between 0.0 and 1.0].
114confidence-threshold = 0.8
115# Allow 1 or more licenses on a per-crate basis, so that particular licenses
116# aren't accepted for every possible crate as with the normal allow list
117exceptions = [
118  # Each entry is the crate and version constraint, and its specific allow
119  # list
120  #{ allow = ["Zlib"], name = "adler32", version = "*" },
121]
122
123# Some crates don't have (easily) machine readable licensing information,
124# adding a clarification entry for it allows you to manually specify the
125# licensing information
126#[[licenses.clarify]]
127# The name of the crate the clarification applies to
128#name = "ring"
129# The optional version constraint for the crate
130#version = "*"
131# The SPDX expression for the license requirements of the crate
132#expression = "MIT AND ISC AND OpenSSL"
133# One or more files in the crate's source used as the "source of truth" for
134# the license expression. If the contents match, the clarification will be used
135# when running the license check, otherwise the clarification will be ignored
136# and the crate will be checked normally, which may produce warnings or errors
137# depending on the rest of your configuration
138#license-files = [
139# Each entry is a crate relative path, and the (opaque) hash of its contents
140#{ path = "LICENSE", hash = 0xbd0eed23 }
141#]
142
143[licenses.private]
144# If true, ignores workspace crates that aren't published, or are only
145# published to private registries.
146# To see how to mark a crate as unpublished (to the official registry),
147# visit https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field.
148ignore = false
149# One or more private registries that you might publish crates to, if a crate
150# is only published to private registries, and ignore is true, the crate will
151# not have its license(s) checked
152registries = [
153  #"https://sekretz.com/registry
154]
155
156# This section is considered when running `cargo deny check bans`.
157# More documentation about the 'bans' section can be found here:
158# https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html
159[bans]
160# Lint level for when multiple versions of the same crate are detected
161multiple-versions = "warn"
162# Lint level for when a crate version requirement is `*`
163wildcards = "allow"
164# The graph highlighting used when creating dotgraphs for crates
165# with multiple versions
166# * lowest-version - The path to the lowest versioned duplicate is highlighted
167# * simplest-path - The path to the version with the fewest edges is highlighted
168# * all - Both lowest-version and simplest-path are used
169highlight = "all"
170# The default lint level for `default` features for crates that are members of
171# the workspace that is being checked. This can be overridden by allowing/denying
172# `default` on a crate-by-crate basis if desired.
173workspace-default-features = "allow"
174# The default lint level for `default` features for external crates that are not
175# members of the workspace. This can be overridden by allowing/denying `default`
176# on a crate-by-crate basis if desired.
177external-default-features = "allow"
178# List of crates that are allowed. Use with care!
179allow = [
180  #{ name = "ansi_term", version = "=0.11.0" },
181]
182# List of crates to deny
183deny = [
184  # Each entry the name of a crate and a version range. If version is
185  # not specified, all versions will be matched.
186  #{ name = "ansi_term", version = "=0.11.0" },
187  #
188  # Wrapper crates can optionally be specified to allow the crate when it
189  # is a direct dependency of the otherwise banned crate
190  #{ name = "ansi_term", version = "=0.11.0", wrappers = [] },
191]
192
193# List of features to allow/deny
194# Each entry the name of a crate and a version range. If version is
195# not specified, all versions will be matched.
196#[[bans.features]]
197#name = "reqwest"
198# Features to not allow
199#deny = ["json"]
200# Features to allow
201#allow = [
202#    "rustls",
203#    "__rustls",
204#    "__tls",
205#    "hyper-rustls",
206#    "rustls",
207#    "rustls-pemfile",
208#    "rustls-tls-webpki-roots",
209#    "tokio-rustls",
210#    "webpki-roots",
211#]
212# If true, the allowed features must exactly match the enabled feature set. If
213# this is set there is no point setting `deny`
214#exact = true
215
216# Certain crates/versions that will be skipped when doing duplicate detection.
217skip = [
218  #{ name = "ansi_term", version = "=0.11.0" },
219]
220# Similarly to `skip` allows you to skip certain crates during duplicate
221# detection. Unlike skip, it also includes the entire tree of transitive
222# dependencies starting at the specified crate, up to a certain depth, which is
223# by default infinite.
224skip-tree = [
225  #{ name = "ansi_term", version = "=0.11.0", depth = 20 },
226]
227
228# This section is considered when running `cargo deny check sources`.
229# More documentation about the 'sources' section can be found here:
230# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.html
231[sources]
232# Lint level for what to happen when a crate from a crate registry that is not
233# in the allow list is encountered
234unknown-registry = "warn"
235# Lint level for what to happen when a crate from a git repository that is not
236# in the allow list is encountered
237unknown-git = "warn"
238# List of URLs for allowed crate registries. Defaults to the crates.io index
239# if not specified. If it is specified but empty, no registries are allowed.
240allow-registry = ["https://github.com/rust-lang/crates.io-index"]
241# List of URLs for allowed Git repositories
242allow-git = []
243
244[sources.allow-org]
245# 1 or more github.com organizations to allow git sources for
246# github = [""]
247# # 1 or more gitlab.com organizations to allow git sources for
248# gitlab = [""]
249# # 1 or more bitbucket.org organizations to allow git sources for
250# bitbucket = [""]