G

Software Supply Chain Security Software

GUAC Software Review

guac.sh · checked 15 Oct 2026

Open-source software supply-chain graph for connecting SBOMs, dependencies, vulnerabilities and evidence.

How it plugs in

—Public API
YesOpen source
YesFree tier

Signal on Software Supply Chain Security Software7.7#1 of 24

GUAC is a self-hosted, open-source system that turns software metadata into a searchable graph. It links SBOMs, packages, dependencies, attestations and security evidence across a portfolio. Developers, operations teams, security practitioners and Open Source Program Offices can inspect risks through APIs or a visualizer.

GUAC home page

Review

In a line

GUAC is an open-source tool for building a connected view of software supply-chain data. It collects metadata such as SBOMs and relates components, packages, dependencies and evidence.

What it does

The system combines information from many projects instead of examining one SBOM at a time. Queries can help locate vulnerable, deprecated, unsupported or duplicated dependencies and flag risky upstream projects with OpenSSF Scorecard data.

A visualizer and query APIs let teams explore the resulting graph. GUAC covers software-security metadata, dependency analysis, SBOM management, build provenance and provenance attestations.

How it connects

GUAC accepts stable formats including SPDX, CycloneDX, CSAF, OpenVEX, DSSE, in-toto ITE6 and OpenSSF Scorecard. Stable enrichment sources include OSV for vulnerabilities, ClearlyDefined for licenses and Deps.dev for dependency details.

Collectors can read or watch local files, storage buckets and Git repositories. Supported blob-storage sources include Azure, Google Cloud Storage, Amazon S3, Memblob and local filesystems. Collectors and certifiers communicate with the ingestor through NATS or the gocloud.dev SDK.

A GraphQL API supports queries and changes to the software-supply-chain model, while a REST API adds health checks and dependency-analysis endpoints. GraphQL definitions are documented as unstable. Data can use in-memory storage or PostgreSQL for persistence.

Good fit

GUAC suits developers, operations and security practitioners, plus Open Source Program Offices that need a portfolio-wide view. It is aimed at teams building a software supply-chain security process around evidence from multiple projects.

It can help organizations correlate SBOMs and related records, investigate dependency exposure and review upstream risk.

Watch for

GUAC is self-hosted. The documented setup uses Docker, Docker Compose and jq, and persistent storage requires operating PostgreSQL and supplying evidence to the graph.

The filesystem collector is stable; other collectors are experimental and may change behavior. ArangoDB and Neo4j/openCypher backends are unsupported and incomplete, while Redis and TiKV keyvalue variants are experimental. An experimental GraphQL filter supports case-insensitive CONTAINS and STARTSWITH comparisons.

Documentation lists MIT for code, while the public repository identifies Apache-2.0 licensing. Check the applicable license and deployment requirements before adoption.

Pricing

GUAC is free and open source. There is no paid plan listed. You provide the infrastructure for Docker Compose and, if needed, PostgreSQL persistence.

Verdict

Choose GUAC if you want to assemble supply-chain evidence from many sources into one queryable graph and can run the service yourself. Its APIs, supported SBOM formats and visualizer fit teams that need cross-project analysis.

It is a poor match for buyers seeking a hosted service or only a single-project SBOM viewer. Experimental collectors, unstable GraphQL definitions and the work of maintaining storage should factor into the decision.

Our take

GUAC makes sense for teams that need one place to connect SBOMs, vulnerability records, dependency details and provenance across many projects. It is especially relevant when engineers or security staff can operate Docker-based infrastructure and maintain a steady flow of evidence. The software costs nothing, but self-hosting, PostgreSQL administration for persistent data and experimental components add operational work. Organizations wanting a hosted product or a simple per-project SBOM tool should consider a different approach.

  • Free and open-source project
  • Connects data across an entire software portfolio
  • Supports SPDX and CycloneDX SBOMs
  • GraphQL, REST and visualizer access
  • Enriches data with OSV, ClearlyDefined and Deps.dev
  • Self-hosted deployment requires Docker, Docker Compose and jq
  • Persistent setups require PostgreSQL operations
  • Several collectors are experimental
  • GraphQL definitions may change
  • Some database backends are unsupported or incomplete
  • Pick it ifSecurity and operations teams correlating supply-chain evidence; Open Source Program Offices managing many projects; Developers investigating dependency and upstream risk
  • Skip it ifYou need a hosted service with no infrastructure to operate; You only need a simple single-SBOM viewer; You require stable support for unsupported database backends

Pricing

GUAC is free and open source. Running it still requires your own infrastructure, with PostgreSQL optional for persistent storage.

  • GUAC (open-source project)Code under MIT license · setup requires Docker, Docker Compose, and jqFree
  • Open-source GUACApache-2.0 licensed · self-hosted · Docker, Docker Compose and jq requiredFree

As docs.guac.sh lists them, checked 7 Oct 2026.

Questions

Is GUAC free?

Yes. GUAC is listed as free and open source. You supply the infrastructure needed to run it.

Which SBOM formats does GUAC support?

Stable ingestion formats include SPDX, CycloneDX, CSAF, OpenVEX, DSSE, in-toto ITE6 and OpenSSF Scorecard.

Does GUAC have an API?

Yes. It provides a GraphQL API and a REST API. The documented GraphQL definitions are unstable and may change.

Where can GUAC run?

GUAC is self-hosted and documented for Linux, macOS and Windows binaries. Setup uses Docker Compose; a web visualizer and APIs are available.

What storage does GUAC use?

It supports an in-memory backend and a PostgreSQL backend for persistent storage. ArangoDB and Neo4j/openCypher are unsupported and incomplete.

What data sources enrich GUAC?

Stable enrichment sources include OSV for vulnerability data, ClearlyDefined for license information and Deps.dev for dependency information.

Who is GUAC for?

The project targets developers, operations and security practitioners, and Open Source Program Offices managing software-supply-chain information.