This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate flowgger

Dependencies

(18 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 capnp ⚠️^0.140.27.2insecure
 clap^44.6.7up to date
 flate2^11.1.10up to date
 glob^0.30.3.4up to date
 kafka^0.80.10.0out of date
 async-nats^0.420.50.0out of date
 log^0.40.4.34up to date
 notify^4.08.2.0out of date
 openssl~0.100.10.81up to date
 rand^0.80.10.3out of date
 redis^0.211.7.1out of date
 serde^11.0.229up to date
 serde_json~0.81.0.151out of date
 may~0.30.3.51up to date
 toml^0.51.1.6+spec-1.1.0out of date
 time^0.30.3.55up to date
 time-tz^0.32.0.0out of date
 tokio^1.45.11.53.1up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tempdir^0.30.3.7up to date
 quickcheck^11.1.0up to date

Build dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 capnpc^0.100.27.0out of date

Security Vulnerabilities

capnp: Unsound APIs of public `constant::Reader` and `StructSchema`

RUSTSEC-2025-0143

The safe API functions constant::Reader::get and StructSchema::new rely on PointerReader::get_root_unchecked, which can cause undefined behavior (UB) by constructing arbitrary words or schemas.

Reader::get

pub fn get(&self) -> Result<<T as Owned>::Reader<'static>> {
    // ...
    // UNSAFE: access `words` without validation
}

StructSchema::new

pub fn new(builder: RawBrandedStructSchema) -> StructSchema {
    // ...
    // UNSAFE: access encoded nodes without validation
}

This vulnerability allows safe Rust code to trigger UB, which violates Rust's safety guarantees.

The issue is resolved in version 0.24.0 by making constructor functions unsafe and mark the fields of struct as visible only in the crate.