rust-lombok-macros
Pass
Audited by Gen Agent Trust Hub on Sep 12, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill manages a surface for indirect prompt injection where user-provided Rust code or transformation requirements are processed. It mitigates this by instructing the agent to strictly preserve domain invariants, avoid exposing mutable internals, and reject requests that bypass security boundaries.\n * Ingestion points: User queries regarding DTO transformations and macro attribute derivations in SKILL.md.\n * Boundary markers: Not explicitly defined for input encapsulation.\n * Capability inventory: File system modification and execution of standard Rust toolchain commands (cargo fmt, check, test, clippy).\n * Sanitization: Extensive guidance on manual review, contract testing, and the use of the CustomDebug macro for secret redaction.\n- [SAFE]: The project uses a pinned Cargo.lock file referencing the official crates.io registry (github.com/rust-lang/crates.io-index), ensuring a verifiable and trusted dependency chain for the lombok-macros crate.\n- [SAFE]: The skill explicitly promotes data privacy and secure coding by instructing users to redact sensitive fields such as tokens and passwords from Debug and Display implementations using provided macro attributes.\n- [SAFE]: Standard Rust development tools (rustc, cargo) are used for environment verification and testing, which is consistent with the skill's stated purpose of Rust code management.
Audit Metadata