Crate cloud_sdk_sanitization 

optional provider-neutral sanitization boundary for cloud-sdk.
Provider crates, explicit API domains, security-first release gates, and transport-free core types.

cloud-sdk crate | Docs.rs | Release Plan | Threat Model | Security

cloud-sdk-sanitization

Optional provider-neutral secret-handling boundary for the main cloud-sdk workspace and cloud-sdk crate.

This crate exists so reusable token, credential, and caller-owned buffer sanitization helpers can be reviewed outside the default no_std SDK and provider crates. It intentionally does not depend on a sanitization implementation yet.

Most users should start with:

[dependencies]
cloud-sdk = "0.12.0"

Use this crate only when the release notes say sanitization helpers have been admitted.

Current Example

use cloud_sdk_sanitization::SanitizationStatus;

assert_eq!(
    SanitizationStatus::DependencyNotAdmitted,
    SanitizationStatus::DependencyNotAdmitted,
);

Security Notes

Sanitization helpers do not replace review of token ownership, copies, logging, environment variables, paging, crash dumps, compiler behavior, or process boundaries. Any future dependency must be admitted with explicit release notes, tests, and pentest evidence.

Enums

SanitizationStatus

Provider-neutral secret-helper readiness state.