rmc-architecture-rules

Rust crate dependency analysis for CI checks detects forbidden producer-to-consumer relationships by building a workspace hypergraph and filtering crate-level edges. It returns structured violation JSON with sample symbols and reference counts for rapid triage.

You can check for forbidden crate dependencies in a Rust CI pipeline by running a forbidden dependency check that outputs structured violation rows. The check provides concrete pass or fail data with sample symbols and reference counts so teams can triage quickly.

Yes, you can use glob-style crate-name patterns to define producer and consumer constraints for crate-edge dependency rules. You can also assign optional per-rule severity levels and custom messages to tailor the architectural layering audit to your specific needs.

A workspace hypergraph in Rust static analysis is used to map and persist crate-level edges across a multi-crate repository. Building this hypergraph is a required step before filtering edges against your declarative dependency rules to find architectural violations.

To troubleshoot Rust crate layering violations detected by static analysis, you review the structured violation JSON containing matching rules, sample symbols, and reference counts. You then pair this triage data with follow-up symbol or file inspection tools to confirm and fix the layering break.