Freedom251 › Container Image Scanning Tools
Google Artifact Analysis

What Google Artifact Analysis is
Google Artifact Analysis provides software composition analysis and structured metadata storage and retrieval. It automatically scans container images pushed to Artifact Registry, then updates vulnerability information as new vulnerabilities are discovered. Package scanning checks Java, Python, and Node.js packages for vulnerabilities, malicious software, secrets, dependencies, and licenses in open-source dependencies. Scans cover packages with 100 or fewer files. Findings and metadata are available in the Google Cloud console, with gcloud CLI, or through the Artifact Analysis API using gRPC or REST/JSON. Metadata can record release activities such as integration tests and vulnerability scans, and can support Binary Authorization policies for compliant images from trusted registries. Detection points are built into products including Artifact Registry and Google Kubernetes Engine. Security Command Center can aggregate Artifact Registry scan findings across projects and export them to BigQuery. Automatic scanning and on-demand scanning each cost $0.26, paid once. Scanned images and packages receive metadata updates while pulled within the last 30 days; results become stale after that. Vulnerability scanning is not supported in Artifact Registry virtual repositories. Google Cloud says it undergoes independent verification and achieves certifications, attestations, and audit reports to help demonstrate compliance.
Who it suits
Artifact Analysis suits teams that need to scan container images and supported language packages or store metadata about release activities. It also fits Google Cloud users who want to access findings through the console, CLI, or API.
What it does well
- Automatically scans images pushed to Artifact Registry.
- Scans Java, Python, and Node.js packages.
- Metadata can support Binary Authorization policies.
- Findings can be exported to BigQuery.
What to know first
- Scans only packages with 100 or fewer files.
- Results become stale after 30 days without pulls.
- Virtual repositories are not supported for vulnerability scanning.
- No free plan is listed.
Limits
Package scanning is limited to packages with 100 or fewer files. Scanned images and packages receive metadata updates while pulled within the last 30 days; afterward, results become stale. Vulnerability scanning is unavailable in Artifact Registry virtual repositories.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| On-Demand Scanning | per scanned container image · Manual scan · results available up to 48 hours after scan completion | $0.26, paid once |
| Automatic scanning | per scan · Container or language package scan · subsequent scans of the same image are free | $0.26, paid once |
As cloud.google.com lists them, read 3 Oct 2026. The maker's own page has the final word.
Getting started
- Visit https://cloud.google.com/artifact-analysis.
- Use the Google Cloud console, gcloud CLI, or Artifact Analysis API.
- Choose automatic scanning or on-demand scanning at $0.26, paid once.
- Push a new image to Artifact Registry for automatic scanning, or request a manual image scan.
Verdict
Artifact Analysis combines package and image scanning with metadata storage and access through Google Cloud interfaces. Account for the package-size and repository limits, and note that scan plans are priced at $0.26, paid once.
Questions
How much does Google Artifact Analysis cost?
Automatic scanning and on-demand scanning are each listed at $0.26, paid once. Automatic scanning is billed per scan, and subsequent scans of the same image are free; on-demand scanning is billed per scanned container image.
Is there a free plan?
No. The service is listed as paid, with scanning plans priced at $0.26, paid once.
Which package types does it scan?
Automatic package scanning supports Java, Python, and Node.js packages. Scans cover packages with 100 or fewer files.
How can users access findings and metadata?
Users can use the Google Cloud console, gcloud CLI, or the Artifact Analysis API, which supports gRPC and REST/JSON.
Does it integrate with other Google Cloud products?
Detection points are built into Artifact Registry and Google Kubernetes Engine. Security Command Center can aggregate Artifact Registry scan findings across projects and export findings to BigQuery.
Can its metadata affect deployment decisions?
Yes. Metadata can be used with Binary Authorization to create policies that allow deployments only for compliant images from trusted registries.
Facts from Google Artifact Analysis's own pages
- Compliance
- Google Cloud says it undergoes independent verification and achieves certifications, attestations, and audit reports to help demonstrate compliance. · cloud.google.com, 3 Oct 2026
- Container scanning
- Automatic vulnerability scanning runs when a new image is pushed to Artifact Registry, and vulnerability information is updated as new vulnerabilities are discovered. · docs.cloud.google.com, 3 Oct 2026
- Deployment policies
- Artifact Analysis metadata can be used with Binary Authorization to create policies that allow deployments only for compliant images from trusted registries. · docs.cloud.google.com, 3 Oct 2026
- Integrations
- Artifact Analysis detection points are built into Google Cloud products including Artifact Registry and Google Kubernetes Engine. · docs.cloud.google.com, 3 Oct 2026
- Metadata
- Artifact Analysis stores and retrieves structured metadata that can record release activities such as integration tests or vulnerability scans. · docs.cloud.google.com, 3 Oct 2026
- Monitoring limit
- Scanned images and packages continue to receive metadata updates while pulled within the last 30 days; after that, results become stale. · docs.cloud.google.com, 3 Oct 2026
- Package scanning
- Package scanning identifies vulnerabilities, malicious software, secrets, dependencies, and licenses in open-source dependencies of language-based packages. · docs.cloud.google.com, 3 Oct 2026
- Purpose
- Artifact Analysis provides software composition analysis and metadata storage and retrieval. · docs.cloud.google.com, 3 Oct 2026
- Repository limitation
- Vulnerability scanning is not supported in Artifact Registry virtual repositories. · docs.cloud.google.com, 3 Oct 2026
- Scanning limit
- Artifact Analysis scans packages with 100 or fewer files. · docs.cloud.google.com, 3 Oct 2026
- Security Command Center
- Security Command Center aggregates Artifact Registry scan findings so users can view image vulnerabilities across projects and export findings to BigQuery. · docs.cloud.google.com, 3 Oct 2026
- Supported interfaces
- Users can access package vulnerabilities and metadata in the Google Cloud console, with gcloud CLI, or through the Artifact Analysis API, which supports gRPC and REST/JSON. · docs.cloud.google.com, 3 Oct 2026
- Supported package types
- Automatic package scanning supports Java, Python, and Node.js packages. · docs.cloud.google.com, 3 Oct 2026
Where Google Artifact Analysis stands on Freedom251
- Container Image Scanning Tools#16 of 29
- Container Security Software#17 of 26
- Cloud Vulnerability Scanners#20 of 28