Repository Content Rules

In addition to catalog entities, a rule can target the files inside a repository. For example, "Does package.json exist and declare React 19 or newer?" or "Does every repository have unit tests?"

A repository content rule can target an explicit list of repositories, or repositories linked to specific catalog entities, and requires that repository to have at least one completed content ingestion before it can be evaluated.

There are three ways to build a repository content rule, from least to most manual:

• Category templates - One-click starting points for common checks (build/test/deploy, tech adoption, security, code quality, and observability).
• Assisted generation - Describe your goal in plain language, and an AI assistant proposes match files and content check expressions based on the target repository's actual content, which you can review and edit before saving. Generated expressions follow the shared operators and repository field rules in Expressions.
• Manual - Write the match files and content check expressions yourself using the repository content expression language (see Expressions).

Every repository content rule can be previewed before saving, showing exactly which files matched and whether each targeted repository passes, fails, or couldn't be evaluated (for example, if that repository has no completed ingestion yet). Preview results are shown per tier.