UiPath Documentation
uipath-cli
latest
false
UiPath CLI user guide

uip rpa analyze

Syntax and options for `uip rpa analyze`, which runs the UiPath workflow analyzer against a Studio project for governance violations.

uip rpa analyze runs the UiPath workflow analyzer against a Studio project, reporting rule violations against a governance policy. It is the modern replacement for uipcli package analyze from the legacy .NET CLI. Refer to Migration — package analyze for the full flag-to-flag map.

Warning:

Runtime requirements

  • .NET runtime must be available on the runner — the workflow analyzer is .NET-backed. Refer to Breaking changes — .NET runtime.
  • Windows runner for Windows projects. Cross-platform projects (targetFramework: "Portable") analyze on any OS. Windows projects (targetFramework: "Windows") require a Windows runner. Refer to uip rpa overview for the full project-flavor matrix.

Synopsis​

uip rpa analyze [project] [options]
uip rpa analyze [project] [options]
  • [project] — path to the Studio project directory, its project.json file, or a .uip archive. Defaults to --project-dir, or the current directory.

For the complete option list on your installed tool version, run:

uip rpa analyze --help
uip rpa analyze --help

Flag names are kebab-case (--governance-file-path, --ignored-rules) rather than the PascalCase used by uipcli.

Policy resolution​

The signed-in tenant is asked for its published Automation Ops policy for the --governance-product product (Development by default):

  • When the tenant publishes a policy, that policy applies. A supplied --governance-file-path is ignored with a warning, and --ignored-rules is not applied.
  • When the tenant publishes none, or the answer cannot be established, the supplied policy file applies.
  • Without a policy file, the analyzer uses the rules shipped with the workflow compiler.

Analyzer and governance options​

FlagDescription
--governance-file-path <path>Path to a governance policy rules JSON file, used when the signed-in tenant publishes no policy.
--governance-file-type <type>How a supplied policy file is read: Default, AutomationOps, or Studio. Defaults to AutomationOps.
--policy-file <path>Alias for --governance-file-path.
--policy-file-type <type>Alias for --governance-file-type.
--governance-product <product>Product whose published Automation Ops policy is resolved, for example Development, Business, or StudioWeb. Defaults to Development. Must not be empty.
--ignored-rules <rules>Comma-separated analyzer rule IDs whose findings are ignored, for example ST-USG-034,ST-MRD-002. Repeat the flag to add more. The rules still run, but their findings are not reported and do not fail the command. Not applied, with a warning, when the signed-in tenant publishes an Automation Ops policy.

Examples​

# Analyze against the tenant's published policy
uip rpa analyze ./MyProject

# Analyze against a local policy file, ignoring two rules
uip rpa analyze ./MyProject --governance-file-path ./policies/governance.json --ignored-rules ST-USG-034,ST-MRD-002
# Analyze against the tenant's published policy
uip rpa analyze ./MyProject

# Analyze against a local policy file, ignoring two rules
uip rpa analyze ./MyProject --governance-file-path ./policies/governance.json --ignored-rules ST-USG-034,ST-MRD-002

Migration from the legacy .NET CLI​

Legacy .NET CLIModern CLI
uipcli package analyze <project>uip rpa analyze <project>
--governance-file-path <policy>--governance-file-path <policy>

Refer to Migration — package analyze for the full flag-level map.

  • uip rpa pack — run before or after packaging.
  • uip rpa restore — ensure dependencies are present on disk so activities resolve for analysis.

See also​

  • Synopsis​
  • Policy resolution​
  • Analyzer and governance options​
  • Examples​
  • Migration from the legacy .NET CLI​
  • Related​
  • See also​

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated