Softwr

Cybersecurity · head to head

Syft vs Wolfi

Syft logo

Syft

Cybersecurity

Generates a software bill of materials from images, filesystems and archives

From
Free
Free plan
Yes
Wolfi logo

Wolfi

Operating Systems

Minimal Linux undistro for containers, sponsored by Chainguard

From
Free
Free plan
Yes

The short version

  • Wolfi is a stripped down Linux distribution for containers.
  • Both are free.
  • Only Syft lists broad ecosystem coverage; only Wolfi lists build time SBOM for every package.
  • Where Wolfi falls short: has no kernel, so it only runs where a container runtime or host supplies one.
  • Prices and features on this page were last checked on 20 November 2026.

How do Syft and Wolfi differ?

Syft and Wolfi differ on pricing model, platforms and category (Cybersecurity against Operating Systems). Only the attributes on which Syft and Wolfi actually diverge.

Attributes where Syft and Wolfi differ
AttributeSyftWolfi
Pricing modelOpen source, no licence feeOpen-source
PlatformsmacOS, Linux, Windows, Self-hostedLinux
CategoryCybersecurityOperating Systems

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 6 appear only for Syft and 7 only for Wolfi. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Syft

  • Multi-format output
  • Broad ecosystem coverage
  • Binary classifiers
  • In-toto attestations
  • Library and CLI
  • Pairs with Grype

Only in Wolfi

  • Build time SBOM for every package
  • Granular independent packages
  • apk package format
  • Declarative reproducible build system
  • glibc support
  • Packages built from source with melange
  • wolfi-base image for trying the distribution

What is each one used for?

Syft is most often brought in for producing a bill of materials for a customer or regulator that requires one; Wolfi for base for minimal container images. The jobs each tool is most often brought in to do.

Syft

  • Producing a bill of materials for a customer or regulator that requires onenot Wolfi
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Wolfi
  • Recording what shipped in a build so a future disclosure can be answered quicklynot Wolfi
  • Public sector work where an SBOM is a contractual deliverablenot Wolfi

Wolfi

  • Base for minimal container imagesnot Syft
  • Building images with apko and melangenot Syft
  • Reducing known vulnerabilities in imagesnot Syft
  • Generating SBOMs for container packagesnot Syft
  • Embedded and containerised workflowsnot Syft

Where do Syft and Wolfi fall short?

Wolfi's most cited limit: has no kernel, so it only runs where a container runtime or host supplies one. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Syft

  • Lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller
  • Fidelity varies sharply by ecosystem. Conan for C and C++, Haskell and Terraform get cataloguer support with no licence data, no dependency relationships and no file ownership, so a C and C++ shop gets the least from it
  • Binary classification yields no licence or dependency metadata, and vendored or statically linked code is exactly where supply chain risk hides, so the blind spot and the risk overlap
  • Incorrect CPE values and CPE collisions are recorded as open issues, and since Grype matches on CPE and PURL, an inventory error becomes a false negative in the security report downstream
  • An inventory is not a risk assessment. Even a perfect bill of materials says a vulnerable version is present, never that the vulnerable function is called, and the triage burden lands entirely on the reader

Wolfi

  • Has no kernel, so it only runs where a container runtime or host supplies one
  • Not aimed at desktop or general server use
  • Repository is a read only clone, so outside pull requests cannot be merged directly
  • apk packages are not compatible with Alpine and mixing distributions is unsupported

How much do Syft and Wolfi cost?

Syft is free to use; Wolfi is free to use. Plan by plan below, from each vendor's own pricing page.

Syft

Free
  • SyftFree
    • Apache-2.0
    • No usage limits
    • Community support
  • Anchore EnterpriseOn request
    • Policy enforcement and reporting
    • Federal and commercial tiers
    • Pricing not published, quoted on request

Wolfi

Free

No published plan breakdown. See the Wolfi review.

Which should you pick?

Choose Syft if

  • You need multi-format output.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Self-hosted.
  • You also want broad ecosystem coverage.

Choose Wolfi if

  • You need build time sbom for every package.
  • You want to start without paying.
  • You work on Linux.
  • You also want granular independent packages.

Questions people ask

Is Syft or Wolfi better?
Neither clearly leads. Syft starts at Free and Wolfi at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Syft or Wolfi?
Syft starts at Free and Wolfi at Free.
Does Syft or Wolfi run on more platforms?
Syft runs on macOS, Linux, Windows, Self-hosted. Wolfi runs on Linux.
Can I use Syft for free?
Both have a free tier, so you can try either at no cost before committing.
What is Syft best used for?
Syft is most often used for producing a bill of materials for a customer or regulator that requires one, feeding an inventory into a vulnerability scanner rather than scanning images directly, recording what shipped in a build so a future disclosure can be answered quickly, public sector work where an sbom is a contractual deliverable. Of those, producing a bill of materials for a customer or regulator that requires one and feeding an inventory into a vulnerability scanner rather than scanning images directly are not what Wolfi is typically brought in for.
What can Syft do that Wolfi cannot?
Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations. Wolfi covers Build time SBOM for every package, Granular independent packages, apk package format, Declarative reproducible build system.

Answered from the vendors’ own pages

Syft: Does Syft find vulnerabilities?

No. It produces an inventory. Grype, from the same company, matches that inventory against vulnerability feeds. They are separate tools and the distinction is frequently lost.

Wolfi: What is Wolfi?

Wolfi is a community Linux undistro built for container and cloud native environments. It has no kernel of its own and uses the one provided by the environment.

Source
Syft: Does anything in the Anchore stack do reachability analysis?

No. Neither Syft, Grype nor the commercial Anchore platform performs call graph or reachability analysis, so none of them tells you whether a vulnerable code path is actually invoked.

Wolfi: Is Wolfi compatible with Alpine packages?

No. Wolfi and Alpine both use apk, but their packages are not compatible, and mixing packages with other distributions is unsupported.

Source
Syft: Is it a CNCF or OpenSSF project?

No. It is single-vendor open source owned by Anchore, with no foundation governance. That is a different licence risk profile from Sigstore.

Wolfi: When was Wolfi announced?

Chainguard announced Wolfi on 22 September 2022. It was introduced as a Linux undistro with supply chain security defaults.

Source
Syft: What does Anchore Enterprise cost?

Not published. The pricing page is contact-sales only, with named but unpriced commercial and federal tiers.

Wolfi: How do I try Wolfi?

Run the wolfi-base image from cgr.dev/chainguard. It is intentionally minimal, so you install tools yourself with apk add.

Source
Syft: How do I know my SBOM is complete?

You largely cannot, which is the honest answer. Silent partial parsing is a known open defect, so a bill of materials used for compliance should be spot-checked against a known dependency list.

Share

Related pages

Other head to heads