I could see a combination of this approach and one of the audit approaches like `cargo crev` working well in the unsafe case: - Require audit if there is new u

I could see a combination of this approach and one of the audit approaches like `cargo crev` working well in the unsafe case: - Require audit if there is new unsafe code - Otherwise, rely on cackle to enforce no use of fs/net etc in safe Rust This could provide the best of both worlds, automating most of the audit burden while still providing strong guarantees.