Skip to content

Commit 05a19df

Browse files
committed
ci: add cargo deny
1 parent 651836c commit 05a19df

6 files changed

Lines changed: 247 additions & 4 deletions

File tree

.github/workflows/ci.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,5 +22,6 @@ jobs:
2222
- run: rustup component add rustfmt clippy
2323
- run: rustc --version
2424
- run: cargo fmt --all --check
25-
- run: cargo clippy -- -D warnings
25+
- run: cargo clippy --workspace --all-targets -- -D warnings
26+
- run: cargo deny check all
2627
- run: cargo test

Cargo.lock

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

deny.toml

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

vectorctl-backend/Cargo.toml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ name = "vectorctl-backend"
33
version = "0.1.0"
44
edition = "2024"
55
publish = false
6+
license-file = "../LICENSE"
67

78
[lib]
89
name = "vectorctl_backend"

vectorctl-migration/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ uuid = { version = "1.16", features = ["atomic", "v7", "zerocopy"] }
2424
once_cell = "1.21"
2525
rustc-hash = "2.0"
2626
futures = "0.3"
27-
tinyvec = "*"
27+
tinyvec = "1.10"
2828
owo-colors = "4.2.3"
2929

3030
[features]

vectorctl-template/Cargo.toml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ name = "vectorctl-template"
33
version = "0.1.0"
44
edition = "2024"
55
publish = false
6+
license-file = "../LICENSE"
67

78
[lib]
89
name = "vectorctl_template"

0 commit comments

Comments
 (0)