Skip to main content

Code Security

A repository is where most of your risk starts and where it's cheapest to fix. The trouble is that a single repository has a dozen kinds of problem: leaked keys, vulnerable dependencies, a CI workflow an outsider can abuse. You don't want twelve tools to see them.

Code Security gives each repository one page. Connect source control and every repository the connection can read appears as a resource.

Prerequisites​

  • A source control connection: GitHub, GitHub Enterprise Server, GitLab, Bitbucket or Azure DevOps. See Integrations.
  • resources:read to see repositories, and scans:run to start a scan.

What gets scanned​

Every full scan runs each category switched on in Scanners, on one snapshot of the repository. For code that means:

  • Your code: static analysis, code quality, secrets, AI code and MCP configuration, skills and agent instructions.
  • What you depend on: vulnerable dependencies, malicious packages, licenses, provenance and signatures.
  • What you ship with it: model files, cryptographic assets and usage, personal data, infrastructure as code, and CI workflows.

A snapshot is one commit of a tracked branch or tag. Dwaar tracks the default branch and the newest tag, and you can add more. See Tracked refs.

Read a repository​

  1. Open Resources, then Code Security.
  2. Select a repository.
  3. Start on Overview for the facts: default branch, language and owners, plus what Dwaar tracks.
  4. Open Findings to see what scanners reported on this repository. Every version has its own findings, so check the version you care about. See Triage findings.
  5. Open Components to see what the newest scan found inside: packages and their licenses, crypto assets, AI components, personal data and attestations.
  6. Open Scans to see every run, what each analyzer did and how long it took.

Scan it now​

Discovery plans scans for you, so you rarely need this. When you do, for example right after a fix lands:

  1. Open the repository.
  2. Select Rescan to re-check scanned refs for new vulnerabilities and scan new snapshots.

You should see a message listing what was queued per ref, such as a vulnerability re-check on one branch and a full scan on another. The run then appears on the Scans tab and in Scan Center.

Use Force rescan only when you want every scanner to run again. Rescans and one-time scans explains the difference.

Organization settings are checked too​

Some problems don't live in any one repository. On GitHub and GitHub Enterprise Server connections, Dwaar also runs a posture check on the organization's security settings, such as branch protection. Those findings count under Code, on the Posture category of the findings list, and they carry no single repository when the setting belongs to the organization.

note

A posture check belongs to the connection, not to a repository, so a repository's Rescan button doesn't start one. Discovery plans it, at most once a day per connection, as long as the Repo settings posture category is on in Scanners.

Try this next​

Pick your most important repository and add a release branch as a tracked ref. Compare the findings on that branch with the default branch. What you're running in production is rarely what's on main.