Skip to content

Commit c9351f4

Browse files
authored
Fix the error given by deny (#446)
* Fix the error given by deny * Allow Unicode-3.0 License
1 parent f1ef1cc commit c9351f4

File tree

2 files changed

+225
-12
lines changed

2 files changed

+225
-12
lines changed

Cargo.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ rand = "0.7.3"
3737
cc = "1.0"
3838

3939
[dev-dependencies]
40-
criterion = "0.4.0"
41-
proptest = "0.9.1"
40+
criterion = "0.5.1"
41+
proptest = "1.5.0"
4242
lazy_static = "1.4.0"
4343

4444
[target.'cfg(not(target_os = "windows"))'.dev-dependencies]

deny.toml

Lines changed: 223 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,239 @@
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.
25+
targets = [
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
45+
all-features = false
46+
# If true, metadata will be collected with `--no-default-features`. The same
47+
# caveat with `all-features` applies
48+
no-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
60+
feature-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
165
[advisories]
2-
vulnerability = "deny"
3-
unmaintained = "warn"
4-
yanked = "deny"
5-
notice = "deny"
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.
72+
ignore = [
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
683

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
787
[licenses]
8-
unlicensed = "deny"
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)].
991
allow = [
1092
"Apache-2.0",
1193
"BSD-2-Clause",
1294
"BSD-3-Clause",
1395
"ISC",
1496
"MIT",
1597
"Unicode-DFS-2016",
98+
"Unicode-3.0",
99+
]
100+
# The confidence threshold for detecting a license from license text.
101+
# The higher the value, the more closely the license text must be to the
102+
# canonical license text of a valid SPDX license file.
103+
# [possible values: any between 0.0 and 1.0].
104+
confidence-threshold = 0.8
105+
# Allow 1 or more licenses on a per-crate basis, so that particular licenses
106+
# aren't accepted for every possible crate as with the normal allow list
107+
exceptions = [
108+
# Each entry is the crate and version constraint, and its specific allow
109+
# list
110+
#{ allow = ["Zlib"], crate = "adler32" },
111+
]
112+
113+
# Some crates don't have (easily) machine readable licensing information,
114+
# adding a clarification entry for it allows you to manually specify the
115+
# licensing information
116+
#[[licenses.clarify]]
117+
# The package spec the clarification applies to
118+
#crate = "ring"
119+
# The SPDX expression for the license requirements of the crate
120+
#expression = "MIT AND ISC AND OpenSSL"
121+
# One or more files in the crate's source used as the "source of truth" for
122+
# the license expression. If the contents match, the clarification will be used
123+
# when running the license check, otherwise the clarification will be ignored
124+
# and the crate will be checked normally, which may produce warnings or errors
125+
# depending on the rest of your configuration
126+
#license-files = [
127+
# Each entry is a crate relative path, and the (opaque) hash of its contents
128+
#{ path = "LICENSE", hash = 0xbd0eed23 }
129+
#]
130+
131+
[licenses.private]
132+
# If true, ignores workspace crates that aren't published, or are only
133+
# published to private registries.
134+
# To see how to mark a crate as unpublished (to the official registry),
135+
# visit https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field.
136+
ignore = false
137+
# One or more private registries that you might publish crates to, if a crate
138+
# is only published to private registries, and ignore is true, the crate will
139+
# not have its license(s) checked
140+
registries = [
141+
#"https://sekretz.com/registry
16142
]
17-
copyleft = "deny"
18-
default = "deny"
19143

144+
# This section is considered when running `cargo deny check bans`.
145+
# More documentation about the 'bans' section can be found here:
146+
# https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html
20147
[bans]
148+
# Lint level for when multiple versions of the same crate are detected
21149
multiple-versions = "warn"
22-
wildcards = "deny"
150+
# Lint level for when a crate version requirement is `*`
151+
wildcards = "allow"
152+
# The graph highlighting used when creating dotgraphs for crates
153+
# with multiple versions
154+
# * lowest-version - The path to the lowest versioned duplicate is highlighted
155+
# * simplest-path - The path to the version with the fewest edges is highlighted
156+
# * all - Both lowest-version and simplest-path are used
157+
highlight = "all"
158+
# The default lint level for `default` features for crates that are members of
159+
# the workspace that is being checked. This can be overridden by allowing/denying
160+
# `default` on a crate-by-crate basis if desired.
161+
workspace-default-features = "allow"
162+
# The default lint level for `default` features for external crates that are not
163+
# members of the workspace. This can be overridden by allowing/denying `default`
164+
# on a crate-by-crate basis if desired.
165+
external-default-features = "allow"
166+
# List of crates that are allowed. Use with care!
167+
allow = [
168+
#"ansi_term@0.11.0",
169+
#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is allowed" },
170+
]
171+
# List of crates to deny
172+
deny = [
173+
#"ansi_term@0.11.0",
174+
#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason it is banned" },
175+
# Wrapper crates can optionally be specified to allow the crate when it
176+
# is a direct dependency of the otherwise banned crate
177+
#{ crate = "ansi_term@0.11.0", wrappers = ["this-crate-directly-depends-on-ansi_term"] },
178+
]
23179

180+
# List of features to allow/deny
181+
# Each entry the name of a crate and a version range. If version is
182+
# not specified, all versions will be matched.
183+
#[[bans.features]]
184+
#crate = "reqwest"
185+
# Features to not allow
186+
#deny = ["json"]
187+
# Features to allow
188+
#allow = [
189+
# "rustls",
190+
# "__rustls",
191+
# "__tls",
192+
# "hyper-rustls",
193+
# "rustls",
194+
# "rustls-pemfile",
195+
# "rustls-tls-webpki-roots",
196+
# "tokio-rustls",
197+
# "webpki-roots",
198+
#]
199+
# If true, the allowed features must exactly match the enabled feature set. If
200+
# this is set there is no point setting `deny`
201+
#exact = true
202+
203+
# Certain crates/versions that will be skipped when doing duplicate detection.
204+
skip = [
205+
#"ansi_term@0.11.0",
206+
#{ crate = "ansi_term@0.11.0", reason = "you can specify a reason why it can't be updated/removed" },
207+
]
208+
# Similarly to `skip` allows you to skip certain crates during duplicate
209+
# detection. Unlike skip, it also includes the entire tree of transitive
210+
# dependencies starting at the specified crate, up to a certain depth, which is
211+
# by default infinite.
212+
skip-tree = [
213+
#"ansi_term@0.11.0", # will be skipped along with _all_ of its direct and transitive dependencies
214+
#{ crate = "ansi_term@0.11.0", depth = 20 },
215+
]
216+
217+
# This section is considered when running `cargo deny check sources`.
218+
# More documentation about the 'sources' section can be found here:
219+
# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.html
24220
[sources]
25-
unknown-registry = "deny"
26-
unknown-git = "deny"
221+
# Lint level for what to happen when a crate from a crate registry that is not
222+
# in the allow list is encountered
223+
unknown-registry = "warn"
224+
# Lint level for what to happen when a crate from a git repository that is not
225+
# in the allow list is encountered
226+
unknown-git = "warn"
227+
# List of URLs for allowed crate registries. Defaults to the crates.io index
228+
# if not specified. If it is specified but empty, no registries are allowed.
229+
allow-registry = ["https://github.com/rust-lang/crates.io-index"]
230+
# List of URLs for allowed Git repositories
231+
allow-git = []
232+
233+
[sources.allow-org]
234+
# github.com organizations to allow git sources for
235+
github = []
236+
# gitlab.com organizations to allow git sources for
237+
gitlab = []
238+
# bitbucket.org organizations to allow git sources for
239+
bitbucket = []

0 commit comments

Comments
 (0)