Skip to main content
Repository settings let you adapt scanning and triage defaults for one codebase. Repository-level values override inherited workspace or organization settings until you reset them.

​
Prerequisites

  • A connected repository in your workspace
  • Permission to manage repository settings
Availability depends on your Cysmiq plan.

​
Steps

1

Open repository settings

Open Repositories under Assets, select the repository, then select Settings.Keep Enable turned on for repositories that Cysmiq should scan. Turning it off stops Cysmiq from running analysis for that repository.
2

Set ownership and the default branch view

Select a Default Assignee when new findings should begin with a specific owner. This supports triage ownership and can be changed on individual findings later.Use Default branch filter to control which branches appear initially on vulnerability views for this repository:
  • Keep Include default branch enabled to include the repository’s default branch.
  • Add exact branch names for other long-lived branches.
  • Add patterns such as release/* when several branches follow the same naming convention.
Repository settings showing Maya Chen as the default assignee and a default branch filter that includes main and release branches.

Repository ownership and default branch filtering for the storefront repository.

These settings change the default view. You can still change filters when reviewing vulnerabilities.
3

Choose the analysis jobs

In Scan jobs, enable the analysis types that should run for this repository:
  • SCA discovers manifests, builds SBOM data, and checks package advisories.
  • Provider checks verify detected credentials with supported providers.
  • Context assessments assess source context when a provider check is unavailable.
  • Secret History searches Git history for exposed secrets.
  • Code analysis scans source code and runs post-processing.
  • Call chains analyze local functions and call paths after code analysis.
Scan job settings showing SCA, secret checks, code analysis, and call chains enabled with main and release branches selected.

Repository scan jobs enabled with call chains limited to selected branch patterns.

4

Scope call-chain analysis

Choose All branches when call-chain analysis should run everywhere. Choose Specific branches and enter comma-separated names or patterns when it should run only on selected branches.Call chains depend on Code analysis. Cysmiq disables both code analysis and Secret History for repositories marked as monorepos.
5

Manage inherited settings

Repository settings inherit workspace or organization values until you save an override. Select Reset overrides in a section to return that repository to inherited values.Configure provider check statuses and pull request decoration separately. See VCS status updates and pull request decoration.