-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdeny.toml
More file actions
70 lines (66 loc) · 2.69 KB
/
Copy pathdeny.toml
File metadata and controls
70 lines (66 loc) · 2.69 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
[graph]
all-features = true
[advisories]
version = 2
# Schema v2 advisory defaults (per cargo-deny):
# - vulnerability: deny (blocks merge on RUSTSEC vulnerabilities)
# - unsound: deny (blocks merge on unsound APIs)
# - unmaintained: warn (surfaces but does not block)
# - notice: warn (surfaces but does not block)
# This matches D9 from the Phase-1 review. To soften a specific advisory
# (e.g. a temporary unmaintained warning we cannot replace yet), add its
# RUSTSEC ID to `ignore` below.
yanked = "deny"
ignore = []
[licenses]
version = 2
# The allowlist mirrors the proposal's Apache-2.0-compatible set. We keep
# entries that aren't currently encountered (e.g. BSD-2-Clause, Zlib,
# Unicode-DFS-2016) so a future dep using them passes without ceremony —
# the proposal already pre-approved them. `unused-allowed-license =
# "allow"` suppresses the bookkeeping warning cargo-deny would otherwise
# emit for each unused entry.
unused-allowed-license = "allow"
allow = [
"Apache-2.0",
"MIT",
"BSD-2-Clause",
"BSD-3-Clause",
"ISC",
"MPL-2.0",
# CDLA-Permissive-2.0 is a permissive *data* license used by webpki-roots
# for the Mozilla CA root bundle. Apache-2.0-compatible.
"CDLA-Permissive-2.0",
"Unicode-3.0",
"Unicode-DFS-2016",
"Unlicense",
"Zlib",
]
confidence-threshold = 0.95
[bans]
multiple-versions = "warn"
wildcards = "deny"
# Acknowledged transitive duplicates. Each entry names *why* the older
# version is in the tree and what it would take to remove it. The
# `multiple-versions = "warn"` policy still fires on new duplicates;
# only the listed pairs are silenced.
skip = [
# `ring` 0.17 pins `getrandom` 0.2 for its rand-source. The rest of
# the tree has moved to 0.4. Remove this skip once ring publishes a
# release that bumps to getrandom 0.3+.
{ crate = "getrandom@0.2.17", reason = "ring 0.17 still pins getrandom 0.2" },
# `ring` 0.17 also pins `windows-sys` 0.52; the rest of the tree
# uses 0.61. Same upstream bump unblocks both.
{ crate = "windows-sys@0.52.0", reason = "ring 0.17 still pins windows-sys 0.52" },
# `wit-bindgen` 0.51 vs 0.57 split lives entirely in the wasi
# target subtree (wasip2 / wasip3 RC). Inactive on our shipped
# targets (linux / macOS / windows); will collapse when the
# wasm-bindgen ecosystem aligns.
{ crate = "wit-bindgen@0.51.0", reason = "wasip3 RC pins an older wit-bindgen than wasip2 (no impact on shipped targets)" },
]
[sources]
unknown-registry = "deny"
unknown-git = "deny"
allow-registry = ["https://github.com/rust-lang/crates.io-index"]
# When introducing a git dependency, add it here as e.g.:
# allow-git = ["https://github.com/no42-org/<repo>"]