Artifact Security
Your repository can be clean while the image you deploy is not. Base images carry their own vulnerabilities, secrets survive in layers a later step "deleted", and nothing in your source tells you any of that.
Artifact Security scans what you actually ship. Connect a registry and its images become resources.
Prerequisites
- A registry connection: Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub, JFrog Artifactory, Harbor, Sonatype Nexus, GitHub Packages, or any OCI registry. See Integrations.
resources:readto see artifacts, andscans:runto start a scan.
What gets scanned
A full scan of an image runs these categories, as long as they're on in Scanners:
| Category | What it answers |
|---|---|
| OS and package vulnerabilities | Are the packages inside this image known to be vulnerable? |
| SBOM | What is in here, in full? Licenses and crypto libraries are read from this scan too |
| Secrets | Are tokens or keys left in a layer, including files a later layer deleted? |
| Crypto assets | Which certificates, keys and TLS settings ship in the image? |
| Attestations | Who built this, and was it altered since? |
| Model file safety | Can a bundled model file run code when it loads? |
| Base image freshness | Which base was this built on, and is it stale or past end of life? |
| Privacy and PII | Is personal data sitting in the application files? |
Multi-architecture images
A tag can point at one manifest or at an index with one manifest per platform. Dwaar treats the index as the snapshot and runs an analyzer per platform, so an arm64 problem doesn't hide behind a clean amd64 result. Tracked refs show each platform and its digest. See Tracked refs.
Read an artifact
- Open Resources, then Artifact Security.
- Select an image.
- On Overview, check the facts: tag, base image, size, digest and registry.
- Open Findings for what scanners reported on this image.
- Open Components for its packages, licenses, crypto, AI components and attestations.
- Open Prove for the documents of the newest scan.
- Open Lineage to see which repository built it.
Scan it now
- Open the image.
- Select Rescan.
You should see one run queued per tracked image tag. Where the snapshot already had a full scan, that run is a vulnerability re-check, which reuses the last SBOM and doesn't pull the image's contents through every scanner again.
Scans run on images. Packages appear as artifacts, but they aren't scanned as resources of their own and offer no scan action.
A finding with no source is half a finding
If an image has no linked repository, Dwaar tells you its findings can't be followed back to their source. A vulnerability in an image you can't trace is one nobody owns. Fixing that link is worth more than triaging another hundred rows. See Lineage.
Try this next
Filter the findings list to Base image freshness. Rebuilding one stale base often closes a long list of inherited vulnerabilities in one move, and it's a far better first fix than patching them one at a time.