Skip to content

refactor(libdd-remote-config)!: hide Target inner properties so they are not leaked#2182

Open
hoolioh wants to merge 2 commits into
mainfrom
julio/remove-common-types-from-rc
Open

refactor(libdd-remote-config)!: hide Target inner properties so they are not leaked#2182
hoolioh wants to merge 2 commits into
mainfrom
julio/remove-common-types-from-rc

Conversation

@hoolioh

@hoolioh hoolioh commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Hide internal implementation so types are not leaked to the consumers

Motivation

Avoid symol/crate duplication on downstream projects.

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jun 30, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 90.48%
Overall Coverage: 74.32% (+0.02%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: fa0a7cd | Docs | Datadog PR Page | Give us feedback!

@github-actions

Copy link
Copy Markdown
Contributor

Clippy Allow Annotation Report

Comparing clippy allow annotations between branches:

  • Base Branch: origin/main
  • PR Branch: origin/julio/remove-common-types-from-rc

Summary by Rule

Rule Base Branch PR Branch Change
expect_used 2 2 No change (0%)
unwrap_used 7 7 No change (0%)
Total 9 9 No change (0%)

Annotation Counts by File

File Base Branch PR Branch Change
datadog-sidecar/src/shm_remote_config.rs 8 8 No change (0%)
libdd-remote-config/src/fetch/fetcher.rs 1 1 No change (0%)

Annotation Stats by Crate

Crate Base Branch PR Branch Change
clippy-annotation-reporter 5 5 No change (0%)
datadog-ffe-ffi 1 1 No change (0%)
datadog-ipc 22 22 No change (0%)
datadog-live-debugger 4 4 No change (0%)
datadog-live-debugger-ffi 10 10 No change (0%)
datadog-profiling-replayer 4 4 No change (0%)
datadog-sidecar 45 45 No change (0%)
libdd-common 13 13 No change (0%)
libdd-common-ffi 12 12 No change (0%)
libdd-data-pipeline 6 6 No change (0%)
libdd-ddsketch 2 2 No change (0%)
libdd-dogstatsd-client 1 1 No change (0%)
libdd-profiling 13 13 No change (0%)
libdd-remote-config 3 3 No change (0%)
libdd-telemetry 20 20 No change (0%)
libdd-tinybytes 4 4 No change (0%)
libdd-trace-normalization 2 2 No change (0%)
libdd-trace-obfuscation 3 3 No change (0%)
libdd-trace-stats 1 1 No change (0%)
libdd-trace-utils 11 11 No change (0%)
Total 182 182 No change (0%)

About This Report

This report tracks Clippy allow annotations for specific rules, showing how they've changed in this PR. Decreasing the number of these annotations generally improves code quality.

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

⚠️ 7459 documentation warning(s) found

📦 datadog-sidecar-ffi - 3056 warning(s)

📦 datadog-sidecar - 2788 warning(s)

📦 libdd-remote-config - 633 warning(s)

📦 libdd-tracer-flare - 982 warning(s)


Updated: 2026-07-01 10:53:56 UTC | Commit: 7a640bf | missing-docs job results

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

⚠️ 27 issue(s) found, showing only errors (advisories, bans, sources)

📦 datadog-sidecar-ffi - 8 error(s)

Show output
error[unsound]: Unsoundness in `Error::downcast_mut()`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:14:1
   │
14 │ anyhow 1.0.93 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
   │
   ├ ID: RUSTSEC-2026-0190
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0190
   ├ Affected versions of this crate violate borrow rules, resulting in undefined behavior, when the user adds context to an error via `Error::context` and then later calls `Error::downcast_mut` on the returned `Error`.
     
     The flaw was corrected in commit `6e8c000` by revising how the mutable reference is constructed, avoiding inclusion of a shared reference in the resulting borrow chain.
     
     ## Example
     
     ```rust
     use anyhow::Error;
     use std::fmt;
     
     #[derive(Debug)]
     struct ErrorContext(&'static str);
     
     impl fmt::Display for ErrorContext {
         fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
             fmt::Display::fmt(&self.0, f)
         }
     }
     
     fn main() {
         let mut error = Error::msg("inner error").context(ErrorContext("old context"));
         let context: &mut ErrorContext = error.downcast_mut().unwrap();
         context.0 = "new context";
         println!("{:?}", error);
     }
     ```
     
     ## Miri output
     
     ```
     error: Undefined Behavior: trying to retag from <1538> for Unique permission at alloc602[0x38], but that tag only grants SharedReadOnly permission for this location
        --> src/ptr.rs:170:18
         |
     170 |         unsafe { &mut *self.ptr.as_ptr() }
         |                  ^^^^^^^^^^^^^^^^^^^^^^^ this error occurs as part of retag at alloc602[0x38..0x48]
         |
         = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
         = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
     help: <1538> was created by a SharedReadOnly retag at offsets [0x38..0x48]
        --> src/ptr.rs:89:18
         |
      89 |             ptr: NonNull::from(ptr),
         |                  ^^^^^^^^^^^^^^^^^^
         = note: stack backtrace:
                 0: anyhow::ptr::Mut::<'_, ErrorContext>::deref_mut
                     at src/ptr.rs:170:18: 170:41
                 1: anyhow::error::<impl anyhow::Error>::downcast_mut::<ErrorContext>
                     at src/error.rs:560:18: 560:46
                 2: main
                     at examples/downcast_mut.rs:15:38: 15:58
     ```
   ├ Announcement: https://github.com/dtolnay/anyhow/issues/451
   ├ Solution: Upgrade to >=1.0.103 (try `cargo update -p anyhow`)
   ├ anyhow v1.0.93
     ├── bolero-engine v0.13.4
     │   ├── bolero v0.13.4
     │   │   ├── (dev) libdd-common-ffi v37.0.0
     │   │   │   ├── datadog-sidecar v0.0.1
     │   │   │   │   └── datadog-sidecar-ffi v0.0.1
     │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   │   │   ├── libdd-crashtracker-ffi v37.0.0
     │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
     │   │   │   └── libdd-telemetry-ffi v37.0.0
     │   │   │       └── datadog-sidecar-ffi v0.0.1 (*)
     │   │   └── (dev) libdd-trace-utils v8.0.0
     │   │       ├── (dev) datadog-sidecar v0.0.1 (*)
     │   │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
     │   │       ├── libdd-data-pipeline v6.0.0
     │   │       │   ├── datadog-live-debugger v0.0.1
     │   │       │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │       │   │   └── datadog-sidecar-ffi v0.0.1 (*)
     │   │       │   └── datadog-sidecar v0.0.1 (*)
     │   │       ├── libdd-trace-obfuscation v4.0.0
     │   │       │   └── libdd-trace-stats v5.0.0
     │   │       │       ├── datadog-ipc v0.1.0
     │   │       │       │   ├── datadog-sidecar v0.0.1 (*)
     │   │       │       │   └── datadog-sidecar-ffi v0.0.1 (*)
     │   │       │       ├── datadog-sidecar v0.0.1 (*)
     │   │       │       └── libdd-data-pipeline v6.0.0 (*)
     │   │       ├── libdd-trace-stats v5.0.0 (*)
     │   │       └── (dev) libdd-trace-utils v8.0.0 (*)
     │   ├── bolero-afl v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   ├── bolero-honggfuzz v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   ├── bolero-kani v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   └── bolero-libfuzzer v0.13.0
     │       └── bolero v0.13.4 (*)
     ├── cc_utils v0.1.0
     │   └── (build) spawn_worker v0.0.1
     │       ├── (dev) datadog-ipc v0.1.0 (*)
     │       └── datadog-sidecar v0.0.1 (*)
     ├── datadog-ipc v0.1.0 (*)
     ├── datadog-live-debugger v0.0.1 (*)
     ├── datadog-sidecar v0.0.1 (*)
     ├── libdd-capabilities v2.0.0
     │   ├── datadog-sidecar v0.0.1 (*)
     │   ├── libdd-capabilities-impl v2.0.0
     │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   ├── libdd-shared-runtime v1.0.0
     │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   │   ├── libdd-telemetry v5.0.1
     │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   │   │   │   ├── libdd-crashtracker v1.0.0
     │   │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   │   │   │   │   └── libdd-crashtracker-ffi v37.0.0 (*)
     │   │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   │   │   ├── libdd-telemetry-ffi v37.0.0 (*)
     │   │   │   │   └── libdd-trace-stats v5.0.0 (*)
     │   │   │   └── libdd-trace-stats v5.0.0 (*)
     │   │   ├── libdd-trace-stats v5.0.0 (*)
     │   │   └── libdd-trace-utils v8.0.0 (*)
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   ├── libdd-shared-runtime v1.0.0 (*)
     │   ├── libdd-trace-stats v5.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-common v5.0.0
     │   ├── datadog-ffe v1.0.0
     │   │   └── datadog-sidecar v0.0.1 (*)
     │   ├── datadog-ipc v0.1.0 (*)
     │   ├── datadog-live-debugger v0.0.1 (*)
     │   ├── datadog-sidecar v0.0.1 (*)
     │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   ├── libdd-capabilities-impl v2.0.0 (*)
     │   ├── libdd-common-ffi v37.0.0 (*)
     │   ├── (build) libdd-crashtracker v1.0.0 (*)
     │   ├── libdd-crashtracker-ffi v37.0.0 (*)
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   ├── libdd-dogstatsd-client v3.0.0
     │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   └── libdd-trace-stats v5.0.0 (*)
     │   ├── libdd-remote-config v1.0.0
     │   │   ├── datadog-ffe v1.0.0 (*)
     │   │   ├── datadog-live-debugger v0.0.1 (*)
     │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
     │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
     │   │   └── (dev) libdd-remote-config v1.0.0 (*)
     │   ├── libdd-shared-runtime v1.0.0 (*)
     │   ├── libdd-telemetry v5.0.1 (*)
     │   ├── libdd-telemetry-ffi v37.0.0 (*)
     │   ├── libdd-trace-obfuscation v4.0.0 (*)
     │   ├── libdd-trace-stats v5.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-common-ffi v37.0.0 (*)
     ├── libdd-crashtracker v1.0.0 (*)
     ├── libdd-crashtracker-ffi v37.0.0 (*)
     ├── libdd-data-pipeline v6.0.0 (*)
     ├── libdd-dogstatsd-client v3.0.0 (*)
     ├── libdd-remote-config v1.0.0 (*)
     ├── libdd-telemetry v5.0.1 (*)
     ├── libdd-trace-normalization v2.0.0
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-trace-obfuscation v4.0.0 (*)
     ├── libdd-trace-stats v5.0.0 (*)
     ├── libdd-trace-utils v8.0.0 (*)
     ├── prost-derive v0.14.3
     │   └── prost v0.14.3
     │       ├── datadog-ffe v1.0.0 (*)
     │       ├── (dev) libdd-data-pipeline v6.0.0 (*)
     │       ├── libdd-ddsketch v1.0.1
     │       │   ├── datadog-ipc v0.1.0 (*)
     │       │   ├── libdd-data-pipeline v6.0.0 (*)
     │       │   ├── libdd-telemetry v5.0.1 (*)
     │       │   └── libdd-trace-stats v5.0.0 (*)
     │       ├── libdd-trace-protobuf v3.0.2
     │       │   ├── datadog-ffe v1.0.0 (*)
     │       │   ├── datadog-ipc v0.1.0 (*)
     │       │   ├── libdd-data-pipeline v6.0.0 (*)
     │       │   ├── libdd-remote-config v1.0.0 (*)
     │       │   ├── libdd-trace-normalization v2.0.0 (*)
     │       │   ├── libdd-trace-obfuscation v4.0.0 (*)
     │       │   ├── libdd-trace-stats v5.0.0 (*)
     │       │   └── libdd-trace-utils v8.0.0 (*)
     │       └── libdd-trace-utils v8.0.0 (*)
     └── spawn_worker v0.0.1 (*)

error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:37:1
   │
37 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     ├── datadog-ipc v0.1.0
     │   ├── datadog-sidecar v0.0.1
     │   │   └── datadog-sidecar-ffi v0.0.1
     │   └── datadog-sidecar-ffi v0.0.1 (*)
     └── datadog-sidecar v0.0.1 (*)

error[unmaintained]: paste - no longer maintained
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:274:1
    │
274 │ paste 1.0.15 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
    │
    ├ ID: RUSTSEC-2024-0436
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2024-0436
    ├ The creator of the crate `paste` has stated in the [`README.md`](https://github.com/dtolnay/paste/blob/master/README.md) 
      that this project is not longer maintained as well as archived the repository
      
      ## Possible Alternative(s)
      
      - [`pastey`]: a fork of paste and is aimed to be a drop-in replacement with additional features for paste crate
      - [`with_builtin_macros`]: crate providing a [superset of `paste`'s functionality including general `macro_rules!` eager expansions](https://docs.rs/with_builtin_macros/0.1.0/with_builtin_macros/macro.with_eager_expansions.html)  and `concat!`/`concat_idents!` macros
      
      [`pastey`]: https://crates.io/crates/pastey
      [`with_builtin_macros`]: https://crates.io/crates/with_builtin_macros
    ├ Announcement: https://github.com/dtolnay/paste
    ├ Solution: No safe upgrade is available!
    ├ paste v1.0.15
      ├── datadog-sidecar-ffi v0.0.1
      ├── libdd-libunwind-sys v1.0.2
      │   └── libdd-crashtracker v1.0.0
      │       ├── datadog-sidecar v0.0.1
      │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │       └── libdd-crashtracker-ffi v37.0.0
      │           ├── datadog-sidecar v0.0.1 (*)
      │           └── datadog-sidecar-ffi v0.0.1 (*)
      ├── libdd-telemetry-ffi v37.0.0
      │   └── datadog-sidecar-ffi v0.0.1 (*)
      └── rmp v0.8.14
          ├── libdd-trace-utils v8.0.0
          │   ├── (dev) datadog-sidecar v0.0.1 (*)
          │   ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-data-pipeline v6.0.0
          │   │   ├── datadog-live-debugger v0.0.1
          │   │   │   ├── datadog-sidecar v0.0.1 (*)
          │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
          │   │   └── datadog-sidecar v0.0.1 (*)
          │   ├── libdd-trace-obfuscation v4.0.0
          │   │   └── libdd-trace-stats v5.0.0
          │   │       ├── datadog-ipc v0.1.0
          │   │       │   ├── datadog-sidecar v0.0.1 (*)
          │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
          │   │       ├── datadog-sidecar v0.0.1 (*)
          │   │       └── libdd-data-pipeline v6.0.0 (*)
          │   ├── libdd-trace-stats v5.0.0 (*)
          │   └── (dev) libdd-trace-utils v8.0.0 (*)
          ├── rmp-serde v1.3.0
          │   ├── datadog-sidecar v0.0.1 (*)
          │   ├── datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-data-pipeline v6.0.0 (*)
          │   ├── (dev) libdd-tinybytes v1.1.1
          │   │   ├── datadog-ipc v0.1.0 (*)
          │   │   ├── datadog-sidecar v0.0.1 (*)
          │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
          │   │   ├── libdd-data-pipeline v6.0.0 (*)
          │   │   ├── (dev) libdd-tinybytes v1.1.1 (*)
          │   │   └── libdd-trace-utils v8.0.0 (*)
          │   ├── libdd-trace-stats v5.0.0 (*)
          │   └── libdd-trace-utils v8.0.0 (*)
          └── rmpv v1.3.0
              └── libdd-trace-utils v8.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:304:1
    │
304 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── datadog-sidecar v0.0.1
      │   └── datadog-sidecar-ffi v0.0.1
      ├── libdd-common v5.0.0
      │   ├── datadog-ffe v1.0.0
      │   │   └── datadog-sidecar v0.0.1 (*)
      │   ├── datadog-ipc v0.1.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   ├── datadog-live-debugger v0.0.1
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   ├── datadog-sidecar v0.0.1 (*)
      │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   ├── libdd-capabilities-impl v2.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   ├── libdd-data-pipeline v6.0.0
      │   │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │   │   └── datadog-sidecar v0.0.1 (*)
      │   │   ├── libdd-shared-runtime v1.0.0
      │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   │   ├── libdd-telemetry v5.0.1
      │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │   │   │   ├── libdd-crashtracker v1.0.0
      │   │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │   │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   │   │   ├── libdd-telemetry-ffi v37.0.0
      │   │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │   │   │   └── libdd-trace-stats v5.0.0
      │   │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │   ├── libdd-trace-stats v5.0.0 (*)
      │   │   └── libdd-trace-utils v8.0.0
      │   │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common-ffi v37.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │   └── libdd-telemetry-ffi v37.0.0 (*)
      │   ├── (build) libdd-crashtracker v1.0.0 (*)
      │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   ├── libdd-dogstatsd-client v3.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   └── libdd-trace-stats v5.0.0 (*)
      │   ├── libdd-remote-config v1.0.0
      │   │   ├── datadog-ffe v1.0.0 (*)
      │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   ├── libdd-shared-runtime v1.0.0 (*)
      │   ├── libdd-telemetry v5.0.1 (*)
      │   ├── libdd-telemetry-ffi v37.0.0 (*)
      │   ├── libdd-trace-obfuscation v4.0.0 (*)
      │   ├── libdd-trace-stats v5.0.0 (*)
      │   └── libdd-trace-utils v8.0.0 (*)
      ├── libdd-crashtracker v1.0.0 (*)
      ├── (dev) libdd-data-pipeline v6.0.0 (*)
      ├── (dev) libdd-ddsketch v1.0.1
      │   ├── datadog-ipc v0.1.0 (*)
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   ├── libdd-telemetry v5.0.1 (*)
      │   └── libdd-trace-stats v5.0.0 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   └── libdd-trace-utils v8.0.0 (*)
      ├── (dev) libdd-trace-stats v5.0.0 (*)
      ├── libdd-trace-utils v8.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── datadog-ipc v0.1.0 (*)
              ├── datadog-sidecar v0.0.1 (*)
              ├── datadog-sidecar-ffi v0.0.1 (*)
              ├── libdd-data-pipeline v6.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v8.0.0 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:334:1
    │
334 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       │       └── datadog-sidecar-ffi v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   ├── libdd-telemetry-ffi v37.0.0
      │   │       │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │   ├── libdd-trace-stats v5.0.0 (*)
      │   │       │   └── libdd-trace-utils v8.0.0
      │   │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
      │   │       │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   │       ├── libdd-common-ffi v37.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       │   └── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── (build) libdd-crashtracker v1.0.0 (*)
      │   │       ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-dogstatsd-client v3.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-remote-config v1.0.0
      │   │       │   ├── datadog-ffe v1.0.0 (*)
      │   │       │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   │       ├── libdd-shared-runtime v1.0.0 (*)
      │   │       ├── libdd-telemetry v5.0.1 (*)
      │   │       ├── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common v5.0.0 (*)
      │   ├── rustls-platform-verifier v0.6.2
      │   │   └── libdd-common v5.0.0 (*)
      │   └── tokio-rustls v0.26.0
      │       ├── hyper-rustls v0.27.7 (*)
      │       └── libdd-common v5.0.0 (*)
      └── rustls-platform-verifier v0.6.2 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:334:1
    │
334 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       │       └── datadog-sidecar-ffi v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   ├── libdd-telemetry-ffi v37.0.0
      │   │       │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │   ├── libdd-trace-stats v5.0.0 (*)
      │   │       │   └── libdd-trace-utils v8.0.0
      │   │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
      │   │       │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   │       ├── libdd-common-ffi v37.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       │   └── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── (build) libdd-crashtracker v1.0.0 (*)
      │   │       ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-dogstatsd-client v3.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-remote-config v1.0.0
      │   │       │   ├── datadog-ffe v1.0.0 (*)
      │   │       │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   │       ├── libdd-shared-runtime v1.0.0 (*)
      │   │       ├── libdd-telemetry v5.0.1 (*)
      │   │       ├── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common v5.0.0 (*)
      │   ├── rustls-platform-verifier v0.6.2
      │   │   └── libdd-common v5.0.0 (*)
      │   └── tokio-rustls v0.26.0
      │       ├── hyper-rustls v0.27.7 (*)
      │       └── libdd-common v5.0.0 (*)
      └── rustls-platform-verifier v0.6.2 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:334:1
    │
334 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       │       └── datadog-sidecar-ffi v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   ├── libdd-telemetry-ffi v37.0.0
      │   │       │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │   ├── libdd-trace-stats v5.0.0 (*)
      │   │       │   └── libdd-trace-utils v8.0.0
      │   │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
      │   │       │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   │       ├── libdd-common-ffi v37.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       │   └── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── (build) libdd-crashtracker v1.0.0 (*)
      │   │       ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-dogstatsd-client v3.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-remote-config v1.0.0
      │   │       │   ├── datadog-ffe v1.0.0 (*)
      │   │       │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   │       │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   │       ├── libdd-shared-runtime v1.0.0 (*)
      │   │       ├── libdd-telemetry v5.0.1 (*)
      │   │       ├── libdd-telemetry-ffi v37.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common v5.0.0 (*)
      │   ├── rustls-platform-verifier v0.6.2
      │   │   └── libdd-common v5.0.0 (*)
      │   └── tokio-rustls v0.26.0
      │       ├── hyper-rustls v0.27.7 (*)
      │       └── libdd-common v5.0.0 (*)
      └── rustls-platform-verifier v0.6.2 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:397:1
    │
397 │ time 0.3.41 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0009
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0009
    ├ ## Impact
      
      When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of
      service attack via stack exhaustion is possible. The attack relies on formally deprecated and
      rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary,
      non-malicious input will never encounter this scenario.
      
      ## Patches
      
      A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned
      rather than exhausting the stack.
      
      ## Workarounds
      
      Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of
      the stack consumed would be at most a factor of the length of the input.
    ├ Announcement: https://github.com/time-rs/time/blob/main/CHANGELOG.md#0347-2026-02-05
    ├ Solution: Upgrade to >=0.3.47 (try `cargo update -p time`)
    ├ time v0.3.41
      ├── libdd-remote-config v1.0.0
      │   ├── datadog-ffe v1.0.0
      │   │   └── datadog-sidecar v0.0.1
      │   │       └── datadog-sidecar-ffi v0.0.1
      │   ├── datadog-live-debugger v0.0.1
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │   └── (dev) libdd-remote-config v1.0.0 (*)
      └── tracing-appender v0.2.3
          └── libdd-log v1.0.0
              └── (dev) libdd-data-pipeline v6.0.0
                  ├── datadog-live-debugger v0.0.1 (*)
                  └── datadog-sidecar v0.0.1 (*)

advisories FAILED, bans ok, sources ok

📦 datadog-sidecar - 7 error(s)

Show output
error[unsound]: Unsoundness in `Error::downcast_mut()`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:14:1
   │
14 │ anyhow 1.0.93 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
   │
   ├ ID: RUSTSEC-2026-0190
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0190
   ├ Affected versions of this crate violate borrow rules, resulting in undefined behavior, when the user adds context to an error via `Error::context` and then later calls `Error::downcast_mut` on the returned `Error`.
     
     The flaw was corrected in commit `6e8c000` by revising how the mutable reference is constructed, avoiding inclusion of a shared reference in the resulting borrow chain.
     
     ## Example
     
     ```rust
     use anyhow::Error;
     use std::fmt;
     
     #[derive(Debug)]
     struct ErrorContext(&'static str);
     
     impl fmt::Display for ErrorContext {
         fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
             fmt::Display::fmt(&self.0, f)
         }
     }
     
     fn main() {
         let mut error = Error::msg("inner error").context(ErrorContext("old context"));
         let context: &mut ErrorContext = error.downcast_mut().unwrap();
         context.0 = "new context";
         println!("{:?}", error);
     }
     ```
     
     ## Miri output
     
     ```
     error: Undefined Behavior: trying to retag from <1538> for Unique permission at alloc602[0x38], but that tag only grants SharedReadOnly permission for this location
        --> src/ptr.rs:170:18
         |
     170 |         unsafe { &mut *self.ptr.as_ptr() }
         |                  ^^^^^^^^^^^^^^^^^^^^^^^ this error occurs as part of retag at alloc602[0x38..0x48]
         |
         = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
         = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
     help: <1538> was created by a SharedReadOnly retag at offsets [0x38..0x48]
        --> src/ptr.rs:89:18
         |
      89 |             ptr: NonNull::from(ptr),
         |                  ^^^^^^^^^^^^^^^^^^
         = note: stack backtrace:
                 0: anyhow::ptr::Mut::<'_, ErrorContext>::deref_mut
                     at src/ptr.rs:170:18: 170:41
                 1: anyhow::error::<impl anyhow::Error>::downcast_mut::<ErrorContext>
                     at src/error.rs:560:18: 560:46
                 2: main
                     at examples/downcast_mut.rs:15:38: 15:58
     ```
   ├ Announcement: https://github.com/dtolnay/anyhow/issues/451
   ├ Solution: Upgrade to >=1.0.103 (try `cargo update -p anyhow`)
   ├ anyhow v1.0.93
     ├── bolero-engine v0.13.4
     │   ├── bolero v0.13.4
     │   │   ├── (dev) libdd-common-ffi v37.0.0
     │   │   │   ├── datadog-sidecar v0.0.1
     │   │   │   └── libdd-crashtracker-ffi v37.0.0
     │   │   │       └── datadog-sidecar v0.0.1 (*)
     │   │   └── (dev) libdd-trace-utils v8.0.0
     │   │       ├── (dev) datadog-sidecar v0.0.1 (*)
     │   │       ├── libdd-data-pipeline v6.0.0
     │   │       │   ├── datadog-live-debugger v0.0.1
     │   │       │   │   └── datadog-sidecar v0.0.1 (*)
     │   │       │   └── datadog-sidecar v0.0.1 (*)
     │   │       ├── libdd-trace-obfuscation v4.0.0
     │   │       │   └── libdd-trace-stats v5.0.0
     │   │       │       ├── datadog-ipc v0.1.0
     │   │       │       │   └── datadog-sidecar v0.0.1 (*)
     │   │       │       ├── datadog-sidecar v0.0.1 (*)
     │   │       │       └── libdd-data-pipeline v6.0.0 (*)
     │   │       ├── libdd-trace-stats v5.0.0 (*)
     │   │       └── (dev) libdd-trace-utils v8.0.0 (*)
     │   ├── bolero-afl v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   ├── bolero-honggfuzz v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   ├── bolero-kani v0.13.0
     │   │   └── bolero v0.13.4 (*)
     │   └── bolero-libfuzzer v0.13.0
     │       └── bolero v0.13.4 (*)
     ├── cc_utils v0.1.0
     │   └── (build) spawn_worker v0.0.1
     │       ├── (dev) datadog-ipc v0.1.0 (*)
     │       └── datadog-sidecar v0.0.1 (*)
     ├── datadog-ipc v0.1.0 (*)
     ├── datadog-live-debugger v0.0.1 (*)
     ├── datadog-sidecar v0.0.1 (*)
     ├── libdd-capabilities v2.0.0
     │   ├── datadog-sidecar v0.0.1 (*)
     │   ├── libdd-capabilities-impl v2.0.0
     │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   ├── libdd-shared-runtime v1.0.0
     │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   │   ├── libdd-telemetry v5.0.1
     │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   │   │   ├── libdd-crashtracker v1.0.0
     │   │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   │   │   │   └── libdd-crashtracker-ffi v37.0.0 (*)
     │   │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   │   │   └── libdd-trace-stats v5.0.0 (*)
     │   │   │   └── libdd-trace-stats v5.0.0 (*)
     │   │   ├── libdd-trace-stats v5.0.0 (*)
     │   │   └── libdd-trace-utils v8.0.0 (*)
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   ├── libdd-shared-runtime v1.0.0 (*)
     │   ├── libdd-trace-stats v5.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-common v5.0.0
     │   ├── datadog-ffe v1.0.0
     │   │   └── datadog-sidecar v0.0.1 (*)
     │   ├── datadog-ipc v0.1.0 (*)
     │   ├── datadog-live-debugger v0.0.1 (*)
     │   ├── datadog-sidecar v0.0.1 (*)
     │   ├── libdd-capabilities-impl v2.0.0 (*)
     │   ├── libdd-common-ffi v37.0.0 (*)
     │   ├── (build) libdd-crashtracker v1.0.0 (*)
     │   ├── libdd-crashtracker-ffi v37.0.0 (*)
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   ├── libdd-dogstatsd-client v3.0.0
     │   │   ├── datadog-sidecar v0.0.1 (*)
     │   │   ├── libdd-data-pipeline v6.0.0 (*)
     │   │   └── libdd-trace-stats v5.0.0 (*)
     │   ├── libdd-remote-config v1.0.0
     │   │   ├── datadog-ffe v1.0.0 (*)
     │   │   ├── datadog-live-debugger v0.0.1 (*)
     │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
     │   │   └── (dev) libdd-remote-config v1.0.0 (*)
     │   ├── libdd-shared-runtime v1.0.0 (*)
     │   ├── libdd-telemetry v5.0.1 (*)
     │   ├── libdd-trace-obfuscation v4.0.0 (*)
     │   ├── libdd-trace-stats v5.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-common-ffi v37.0.0 (*)
     ├── libdd-crashtracker v1.0.0 (*)
     ├── libdd-crashtracker-ffi v37.0.0 (*)
     ├── libdd-data-pipeline v6.0.0 (*)
     ├── libdd-dogstatsd-client v3.0.0 (*)
     ├── libdd-remote-config v1.0.0 (*)
     ├── libdd-telemetry v5.0.1 (*)
     ├── libdd-trace-normalization v2.0.0
     │   ├── libdd-data-pipeline v6.0.0 (*)
     │   └── libdd-trace-utils v8.0.0 (*)
     ├── libdd-trace-obfuscation v4.0.0 (*)
     ├── libdd-trace-stats v5.0.0 (*)
     ├── libdd-trace-utils v8.0.0 (*)
     ├── prost-derive v0.14.3
     │   └── prost v0.14.3
     │       ├── datadog-ffe v1.0.0 (*)
     │       ├── (dev) libdd-data-pipeline v6.0.0 (*)
     │       ├── libdd-ddsketch v1.0.1
     │       │   ├── datadog-ipc v0.1.0 (*)
     │       │   ├── libdd-data-pipeline v6.0.0 (*)
     │       │   ├── libdd-telemetry v5.0.1 (*)
     │       │   └── libdd-trace-stats v5.0.0 (*)
     │       ├── libdd-trace-protobuf v3.0.2
     │       │   ├── datadog-ffe v1.0.0 (*)
     │       │   ├── datadog-ipc v0.1.0 (*)
     │       │   ├── libdd-data-pipeline v6.0.0 (*)
     │       │   ├── libdd-remote-config v1.0.0 (*)
     │       │   ├── libdd-trace-normalization v2.0.0 (*)
     │       │   ├── libdd-trace-obfuscation v4.0.0 (*)
     │       │   ├── libdd-trace-stats v5.0.0 (*)
     │       │   └── libdd-trace-utils v8.0.0 (*)
     │       └── libdd-trace-utils v8.0.0 (*)
     └── spawn_worker v0.0.1 (*)

error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:37:1
   │
37 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     ├── datadog-ipc v0.1.0
     │   └── datadog-sidecar v0.0.1
     └── datadog-sidecar v0.0.1 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:302:1
    │
302 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── datadog-sidecar v0.0.1
      ├── libdd-common v5.0.0
      │   ├── datadog-ffe v1.0.0
      │   │   └── datadog-sidecar v0.0.1 (*)
      │   ├── datadog-ipc v0.1.0
      │   │   └── datadog-sidecar v0.0.1 (*)
      │   ├── datadog-live-debugger v0.0.1
      │   │   └── datadog-sidecar v0.0.1 (*)
      │   ├── datadog-sidecar v0.0.1 (*)
      │   ├── libdd-capabilities-impl v2.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   ├── libdd-data-pipeline v6.0.0
      │   │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │   │   └── datadog-sidecar v0.0.1 (*)
      │   │   ├── libdd-shared-runtime v1.0.0
      │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   │   ├── libdd-telemetry v5.0.1
      │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │   ├── libdd-crashtracker v1.0.0
      │   │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │   │   │   │       └── datadog-sidecar v0.0.1 (*)
      │   │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v5.0.0
      │   │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │   ├── libdd-trace-stats v5.0.0 (*)
      │   │   └── libdd-trace-utils v8.0.0
      │   │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common-ffi v37.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   └── libdd-crashtracker-ffi v37.0.0 (*)
      │   ├── (build) libdd-crashtracker v1.0.0 (*)
      │   ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   ├── libdd-dogstatsd-client v3.0.0
      │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │   └── libdd-trace-stats v5.0.0 (*)
      │   ├── libdd-remote-config v1.0.0
      │   │   ├── datadog-ffe v1.0.0 (*)
      │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   ├── libdd-shared-runtime v1.0.0 (*)
      │   ├── libdd-telemetry v5.0.1 (*)
      │   ├── libdd-trace-obfuscation v4.0.0 (*)
      │   ├── libdd-trace-stats v5.0.0 (*)
      │   └── libdd-trace-utils v8.0.0 (*)
      ├── libdd-crashtracker v1.0.0 (*)
      ├── (dev) libdd-data-pipeline v6.0.0 (*)
      ├── (dev) libdd-ddsketch v1.0.1
      │   ├── datadog-ipc v0.1.0 (*)
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   ├── libdd-telemetry v5.0.1 (*)
      │   └── libdd-trace-stats v5.0.0 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   ├── libdd-data-pipeline v6.0.0 (*)
      │   └── libdd-trace-utils v8.0.0 (*)
      ├── (dev) libdd-trace-stats v5.0.0 (*)
      ├── libdd-trace-utils v8.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── datadog-ipc v0.1.0 (*)
              ├── datadog-sidecar v0.0.1 (*)
              ├── libdd-data-pipeline v6.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v8.0.0 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:332:1
    │
332 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       └── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │   ├── libdd-trace-stats v5.0.0 (*)
      │   │       │   └── libdd-trace-utils v8.0.0
      │   │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   │       ├── libdd-common-ffi v37.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── (build) libdd-crashtracker v1.0.0 (*)
      │   │       ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-dogstatsd-client v3.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-remote-config v1.0.0
      │   │       │   ├── datadog-ffe v1.0.0 (*)
      │   │       │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   │       ├── libdd-shared-runtime v1.0.0 (*)
      │   │       ├── libdd-telemetry v5.0.1 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common v5.0.0 (*)
      │   ├── rustls-platform-verifier v0.6.2
      │   │   └── libdd-common v5.0.0 (*)
      │   └── tokio-rustls v0.26.0
      │       ├── hyper-rustls v0.27.7 (*)
      │       └── libdd-common v5.0.0 (*)
      └── rustls-platform-verifier v0.6.2 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:332:1
    │
332 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       └── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │   ├── libdd-trace-stats v5.0.0 (*)
      │   │       │   └── libdd-trace-utils v8.0.0
      │   │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │       ├── libdd-trace-obfuscation v4.0.0
      │   │       │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       │       └── (dev) libdd-trace-utils v8.0.0 (*)
      │   │       ├── libdd-common-ffi v37.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   └── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── (build) libdd-crashtracker v1.0.0 (*)
      │   │       ├── libdd-crashtracker-ffi v37.0.0 (*)
      │   │       ├── libdd-data-pipeline v6.0.0 (*)
      │   │       ├── libdd-dogstatsd-client v3.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   └── libdd-trace-stats v5.0.0 (*)
      │   │       ├── libdd-remote-config v1.0.0
      │   │       │   ├── datadog-ffe v1.0.0 (*)
      │   │       │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │   │       │   └── (dev) libdd-remote-config v1.0.0 (*)
      │   │       ├── libdd-shared-runtime v1.0.0 (*)
      │   │       ├── libdd-telemetry v5.0.1 (*)
      │   │       ├── libdd-trace-obfuscation v4.0.0 (*)
      │   │       ├── libdd-trace-stats v5.0.0 (*)
      │   │       └── libdd-trace-utils v8.0.0 (*)
      │   ├── libdd-common v5.0.0 (*)
      │   ├── rustls-platform-verifier v0.6.2
      │   │   └── libdd-common v5.0.0 (*)
      │   └── tokio-rustls v0.26.0
      │       ├── hyper-rustls v0.27.7 (*)
      │       └── libdd-common v5.0.0 (*)
      └── rustls-platform-verifier v0.6.2 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:332:1
    │
332 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v5.0.0
      │   │       ├── datadog-ffe v1.0.0
      │   │       │   └── datadog-sidecar v0.0.1
      │   │       ├── datadog-ipc v0.1.0
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-live-debugger v0.0.1
      │   │       │   └── datadog-sidecar v0.0.1 (*)
      │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       ├── libdd-capabilities-impl v2.0.0
      │   │       │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-data-pipeline v6.0.0
      │   │       │   │   ├── datadog-live-debugger v0.0.1 (*)
      │   │       │   │   └── datadog-sidecar v0.0.1 (*)
      │   │       │   ├── libdd-shared-runtime v1.0.0
      │   │       │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   ├── libdd-telemetry v5.0.1
      │   │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-crashtracker v1.0.0
      │   │       │   │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   │   └── libdd-crashtracker-ffi v37.0.0
      │   │       │   │   │   │       └── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │   ├── libdd-data-pipeline v6.0.0 (*)
      │   │       │   │   │   └── libdd-trace-stats v5.0.0
      │   │       │   │   │       ├── datadog-ipc v0.1.0 (*)
      │   │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │   │       │   │   │       └── libdd-data-pipeline v6.0.0 (*)
      │   │      ...*[Comment body truncated]*

@hoolioh hoolioh force-pushed the julio/remove-common-types-from-rc branch from 443c3a9 to 513ee52 Compare June 30, 2026 11:21
@dd-octo-sts

dd-octo-sts Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 85.13 MB 85.13 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 7.82 MB 7.82 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.51 MB 10.51 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 96.27 MB 96.27 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 25.18 MB 25.18 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 88.04 KB 88.04 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 183.48 MB 183.47 MB -0% (-8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 939.61 MB 939.62 MB +0% (+9.94 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.23 MB 8.23 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 88.04 KB 88.04 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 24.33 MB 24.33 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 48.49 MB 48.49 MB 0% (0 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 21.81 MB 21.81 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 89.42 KB 89.42 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 187.48 MB 187.48 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 926.73 MB 926.74 MB +0% (+9.99 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.35 MB 6.35 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 89.42 KB 89.42 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 26.10 MB 26.10 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 46.12 MB 46.12 MB 0% (0 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 75.88 MB 75.88 MB 0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 8.70 MB 8.70 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 91.34 MB 91.34 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.59 MB 10.59 MB 0% (0 B) 👌

@hoolioh hoolioh marked this pull request as ready for review June 30, 2026 13:09
@hoolioh hoolioh requested review from a team as code owners June 30, 2026 13:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 513ee52576

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


pub use libdd_common::{tag::Tag, Endpoint};

use serde::{Deserialize, Serialize};

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the Endpoint re-export

When consumers construct the public fetch::ConfigInvariants, its endpoint field still has type libdd_common::Endpoint, but this hunk removes the only libdd_remote_config::Endpoint re-export. In downstream crates that only depend on libdd-remote-config, this forces adding a direct libdd-common dependency pinned to the exact same version and can reintroduce the duplicate-crate problem this change is trying to avoid; keep re-exporting Endpoint while dropping only Tag.

Useful? React with 👍 / 👎.

Comment thread libdd-remote-config/src/lib.rs Outdated
@hoolioh hoolioh force-pushed the julio/remove-common-types-from-rc branch from f09c1ad to fa0a7cd Compare July 1, 2026 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants