What this check looks at
Whether the repository is public and active, whether its main branch is protected, whether it publishes a security policy, its OpenSSF Scorecard and its licence.
Free tool
How well protected is this repository?
Runs in your browser – nothing is saved to an account.
What each part of the answer means, and what to do when one is not right.
Enter a public GitHub or GitLab repository – an https:// or git@ address – and Xovris reads its health from the code host and OpenSSF Scorecard in your browser.
Whether the repository is public and active, whether its main branch is protected, whether it publishes a security policy, its OpenSSF Scorecard and its licence.
An unprotected main branch lets anyone with write access push to it or rewrite its history. Without a security policy, someone who finds a flaw has no private way to report it. A low Scorecard names what to harden first.
Connect the repository and Xovris takes this on as a coding job: it writes the SECURITY.md and works through the Scorecard checks in order on a copy, each change in a pull request your own checks prove, and keeps the repository’s protections in view. The branch rule that requires reviews and passing checks is set by an owner of the repository in its settings. Do it yourself instead: add that branch rule, publish a SECURITY.md and work through the Scorecard checks in order.
Straight answers, from what the check itself does.
Add your site to Xovris on the Free plan and this check runs every 3 minutes, with an alert by email or Slack when it fails. On Personal, Xovris investigates the cause, makes the change its finding names and proves the fix.