What is a resource?
You can't secure what you can't list. Most teams find that out when a scanner reports on the repositories it was pointed at and stays silent about the ones nobody remembered.
A resource is anything Dwaar watches: a repository, a container image, an AWS account, a Lambda function. Resources are the rows everything else hangs off. Scans run against them, findings land on them, and lineage connects them.
You don't create most resources by hand. Connect an integration and discovery lists what that connection holds. See How discovery and scans work.
The seven resource types
| Type | What it covers | Row noun | Available today |
|---|---|---|---|
| Code Security | Repositories, what Dwaar scans there and what it found | Repository | Yes |
| Artifact Security | Container images, packages, models and mobile apps you ship | Artifact | Yes |
| Cloud & Workloads | Accounts and the workloads running in them | Cloud resource | Yes |
| API Security | APIs and web apps you expose | API | Preview |
| AI Agent Security | Agents and MCP servers your products use | Agent | Preview |
| Vendor Risk Assessment | Third parties your products depend on | Vendor | Preview |
| Build Tool Security | Pipelines, runners and developer devices | Build tool | Preview |
The practical rule: if you connect source control, a registry, and AWS, Vercel, Railway or Cloudflare, the first three types fill in. Those are the types with scanners behind them today.
Read the Resources page as a coverage map
Open Resources in the left rail. Each type gets a pane with four numbers:
| Number | What it tells you |
|---|---|
| Total | How many resources of this type Dwaar knows about |
| Scanned, tested or checked | How many have actually been looked at |
| Not scanned, tested or checked | How many have not. This is your blind spot |
| Open findings | Findings still open on this type |
The verb changes on purpose. Repositories and images are scanned, cloud assets are checked, and APIs and agents are tested.
A pane can also carry a notice such as "No registry connected". Take that seriously. A pane with zero findings and that notice doesn't mean you're safe. It means nobody looked.
Tabs change by type
Open a resource and the tabs tell you what can be done to it. Dwaar doesn't show you a tab that can't apply.
| Type | Tabs |
|---|---|
| Code, Artifact | Overview, Lineage, Findings, Components, Scans, Guard, Prove, Fix, Break |
| Cloud | Overview, Lineage, Findings, Scans, Guard, Fix. An account adds Workloads |
| API, AI Agent | Overview, Lineage, Connector, Findings, Guard, Prove, Fix, Break |
| Vendor, Build tool | Overview, Lineage, Findings, Guard, Prove, Fix, Break |
Findings holds what scanners reported. Components shows what the newest scan found inside the resource. Scans lists every run. Guard, Fix, Break and Connector are in preview.
Try this next
Open the pane with the largest "Not scanned" number and find out why. That one number tells you more about your real coverage than the findings count does.