A dependency update can change what your program is allowed to do
A capsec diff of two published Rust crate versions shows why dependency review should include newly reachable filesystem, network, process, and FFI behavior.
Verification
3 entries exploring this thread.
A function signature should say what the function can do
How capsec makes filesystem and network authority visible in Rust types, what the compiler rejects, and where audit must take over.
The repository rejects reverse dependencies
How auths-proof turns layer direction, offline verification, deterministic CBOR, and protocol bounds into executable repository checks.