Vetrix Docs

Security

The Security page gives an administrator a single, instance-wide view of vulnerability counts across every repository, and the Policy section lets you edit the instance-default rules that gate merges and deployments. This page covers reading the security summary, opening the accessible data tables, and editing, previewing, and restoring the instance policy.

Where to find it

Open your avatar menu in the top navigation bar and select Admin panel, or go to gitvetrix.com/admin directly. In the admin sidebar, under Access & Security, select Security for the summary or Policy for the instance-default policy.

URL patterns: gitvetrix.com/admin/security and gitvetrix.com/admin/security/policy

Read the security summary

The Security Summary page shows aggregate vulnerability counts across all repositories in the instance. It is read-only: to act on a finding, follow a repository link to that repository's own security view.

  • Totals by severity shows one card per severity — Critical, High, Medium, Low, and Info — with the total count of open findings at that level across the instance.
  • Per-repository breakdown lists each repository that has been scanned, most affected first. Each row links to the repository and shows its counts for every severity, a Secrets count of open secret alerts, and how long ago it was last scanned.

If no scans have run anywhere, the page shows No security data. If scans have run but no repository currently has findings, the breakdown shows No repositories with scans.

Show the data behind a summary

Each part of the summary can be read as a plain table.

  1. Under Totals by severity or Per-repository breakdown, select Show data table.
  2. Read the table that appears, with a row for each severity or repository.
  3. Select Hide data table to collapse it again.

Edit the instance-default policy

The Policy page, titled Instance-default security policy, holds the rules that the merge and deploy gates evaluate. Saving takes effect on the next scan evaluation, with no server restart.

  1. Use the Gate selector to choose which gate you are editing: merge or deploy. The line above the editor shows which gate and version you are working on, or notes that you are editing the embedded default when no version has been saved yet.
  2. Edit the policy source in the editor.
  3. Select Lint to check the source. If it does not parse, each error appears beneath the editor with its line and column.
  4. Select Save new version to store your changes. If the source fails validation on save, the errors appear beneath the editor and nothing is saved.

Preview a policy before saving

The Preview panel evaluates your edited policy against a sample input so you can see the result the real gate would produce.

  1. In the Preview panel, edit the fixture — the sample input in the text box — or leave the default in place. Select Reset fixture to return it to the default at any time.
  2. Select Preview.
  3. Read the result: an ALLOW or DENY badge with the evaluation time, and, when the policy denies the input, the list of reasons. If the fixture is not valid, a message explains what is wrong instead.

Restore a previous policy version

The History panel lists saved versions of the current gate's policy, newest first, each marked with its version number.

  1. In History, find the version you want to return to.
  2. Select Restore next to it. The editor loads that version's source as a new version, and a confirmation notes the new version number.
  3. Review the restored source, then select Save new version if you want to keep further edits.

When no versions have been saved yet, the panel notes that the editor is showing the embedded default.