One code health workflow across the languages teams actually ship.
Iris Code is built for mixed repos, not single-language demos. The strongest coverage today is TypeScript and JavaScript, with Go and Python included in the same scoring and secrets-detection story so the whole repo can move toward one enforceable standard.
TypeScript & JavaScript
TypeScript & JavaScript
Full coverageThe deepest analysis Iris Code offers. Full file scoring, complexity analysis, function-level signals, import analysis, secrets detection, and type-safety-aware checks that are specific to TypeScript.
Go
Go
Good coverageFile scoring, complexity, function size, code smells, and secrets coverage for backend and service code. Import analysis is partial. Type-safety checks are not applicable to Go.
Python
Python
Good coverageComplexity, code smells, and secrets scanning for scripts and services so mixed-language repos still get one local-first score workflow. Function-level and import analysis are partial.
Use Iris Code where local-first signal matters most
Start with the files people touch most, commit one shared configuration, and only then turn on enforcement. That rollout pattern matters more than chasing perfect language parity on day one.