Português

Settings

What is real here: the PR-gate policy is the actual sovra-policy.json the CI gate reads. The tracker profile is saved in this browser only, to prefill Publish. Roles are read live from the enforcement layer.

Enter your API key in the field at the top of the page to load your policy and roles.

PR-gate / compliance policy

Your tenant's own gate policy, stored server-side. The CLI's sovra gate reads a local sovra-policy.json; export this one there to use the same rules in CI.

Score floors

0 means no minimum. A scan scoring below a floor fails the gate.

Forbidden signals

Flags that fail the gate outright
Jurisdictions forbidden for runtime components
Baseline gate: a new flag fails even when existing ones are accepted debt.
Fail if a dependency newly enters one of these jurisdictions

License policy

Forbidden license classes
Reach-aware: build-only copyleft does not trip these.
Comma-separated.
Noisy on real dependency trees, so it is opt-in.

Tracker integration profile

Saved in this browser's local storage only. It is never sent to Sovra's server except when you click Publish tickets on a scan. It prefills the Publish panel so you stop retyping it.

owner/repo that receives the issues.
A GitHub token or a Jira API token.

Roles & access Read-only

Live from the enforcement layer (governance.ROLES), not a separate ACL that can drift out of sync. Explicit-actor forms elsewhere ask you to pick one of these; the server re-checks it on every call regardless of what the form allowed you to select.

RoleScopeMay invoke