Monorepo intelligence

Full workflow

Complete guide (limitations, CI, published lens): monorepo-intelligence

Why use CCE

Monorepos hide cloud and SDK usage across packages. Platform and security teams can't enforce standards when which packages call which APIs is unknown. Per-package dependency files don't reflect transitive call paths through shared internal libraries.

CCE scans the monorepo (or per-package subtrees) and clusters call sites by directory to expose cross-package cloud and SDK usage patterns.

Example command

cce -folder . -language AUTO -mapper-file https://releases.stackgen.com/cce/lenses/monorepo-intelligence/latest/monorepo-intelligence_lenses.yaml -filter all -format json -output monorepo-intelligence.json

Published lens

https://releases.stackgen.com/cce/lenses/monorepo-intelligence/latest/monorepo-intelligence_lenses.yaml