rtb-telemetry 0.7.2

Opt-in anonymous usage telemetry with pluggable sinks. Part of the phpboyscout Rust toolkit.
Documentation
# cargo-deny configuration.
# https://embarkstudios.github.io/cargo-deny/
#
# No advisory waivers: this crate's graph is lean enough to carry none.
# If one becomes necessary, copy the monorepo's waiver discipline โ€”
# advisory ID, the reaching chain, and a dated sunset condition.

[advisories]
db-urls = ["https://github.com/rustsec/advisory-db"]
yanked = "deny"

[licenses]
allow = [
    "MIT",
    "MIT-0",
    "Apache-2.0",
    "Apache-2.0 WITH LLVM-exception",
    "BSD-2-Clause",
    "BSD-3-Clause",
    "ISC",
    "Unicode-DFS-2016",
    "Unicode-3.0",
    "Zlib",
    "CC0-1.0",
    "MPL-2.0",
    "0BSD",
    # Community Data License โ€” used by webpki-root-certs (via reqwest's
    # rustls platform verifier) under the `remote-sinks` feature. Same
    # allowance the monorepo carries for webpki-roots.
    "CDLA-Permissive-2.0",
]
confidence-threshold = 0.8

[bans]
multiple-versions = "warn"
wildcards = "deny"
# The enforceable "framework-free" statement (extraction playbook ยง2.2):
# this crate must never depend back on the tool, and never regress onto
# the workspace-banned crates.
deny = [
    { crate = "rust-tool-base" },
    { crate = "rtb-cli-bin" },
    # anyhow is banned from library code (thiserror + miette are the
    # error surface); cucumber pulls it as a dev-only transitive, which
    # matches the workspace policy "anyhow in tests is acceptable".
    # prost-derive (a proc-macro, build-time only โ€” never linked into
    # the shipped library) pulls it under the `remote-sinks` OTLP
    # stack; per `cargo tree -i anyhow --all-features` those are the
    # only two reaching chains.
    { crate = "anyhow", wrappers = ["cucumber", "prost-derive"] },
    { crate = "openssl-sys" },
    { crate = "native-tls" },
]

[sources]
unknown-registry = "deny"
unknown-git = "deny"
allow-registry = ["https://github.com/rust-lang/crates.io-index"]