Skip to main content
Preview. This part of the console is still being built. What you see here describes the intended behavior and can change before general availability.

Vendor and build tool security

Your software is built by tools you didn't write and depends on companies you don't control. Both can hurt you, and neither shows up in a repository scan.

These two resource types put them on the same map as your code.

note

This page describes a preview. The screens exist in the console and can change before release. Vendors can already be discovered: connect an identity provider or upload an expense export, as Identity and SaaS describes. Discovering build tools isn't available yet.

What each type holds​

TypeKindsFacts it tracks
Vendor Risk AssessmentVendor, SaaS appRisk tier, SOC 2, data shared, vendor SBOM, OAuth grants, whether it trains on your data
Build Tool SecurityPipeline, runner, device fleetRunner, last run, OS, ephemeral, egress, devices, device manager

What stays unknown until you connect​

Each type names the gap it can't fill by itself:

  • Without an identity provider, Dwaar can't know which SaaS apps your people sign in to. Connect one to fill this gap.
  • Without a CI integration, workflow and runner security stay unknown.
  • Without a device manager, device posture and the local MCP and AI tools on developer machines stay unknown.

What you can check today​

The pipeline itself isn't a blind spot, even in preview. Two things run now on repositories, and they cover real ground:

CategoryWhere it runsWhat it finds
CI workflow securityCode scansWays an outsider could run code or steal build secrets through your pipeline files
Repo settings postureGitHub connectionsWeak organization and repository settings, such as branch protection

Both are listed in Scanners, under Code.

For third parties, the Privacy group in Components shows which SDKs in your code and images receive personal data, and which data they get. That's a concrete vendor list, built from what you ship and not from a spreadsheet.

Try this next​

Open the Misconfiguration category of the findings list and filter Type to CI workflow. A pipeline that an outsider can trigger is a short path to your build secrets, so it's a good place to spend your first hour.