Softwr

Cybersecurity · head to head

Syft vs VUEWorks

Syft logo

Syft

Cybersecurity

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

From
Free
Free plan
Yes
Full reviewWebsite
VUEWorks logo

VUEWorks

Government

GIS-centred enterprise asset management for public agencies, built around Esri ArcGIS

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Syft has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; VUEWorks the product assumes a maintained enterprise ArcGIS geodatabase; agencies without one face a spatial data cleanup project before VUEWorks does anything useful, and that project is usually quoted by the same consultancy selling the software.
  • They diverge on capability: Syft covers Multi-format output, VUEWorks covers Native Esri integration.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Syft and VUEWorks actually diverge.

Attributes where Syft and VUEWorks differ
AttributeSyftVUEWorks
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsmacOS, Linux, Windows, DockerWeb, iOS, Android
CategoryCybersecurityGovernment

Identical on both: user rating (Not yet rated).

What each one covers

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 VUEWorks

  • Native Esri integration
  • Work orders and requests
  • Inspections
  • Condition and risk
  • Capital planning
  • Pavement management
  • Mobile field access
  • Dashboards

What people use each for

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 VUEWorks
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot VUEWorks
  • Recording what shipped in a build so a future disclosure can be answered quicklynot VUEWorks
  • Public sector work where an SBOM is a contractual deliverablenot VUEWorks

VUEWorks

  • A county public works department that already runs Esri and wants work orders raised directly against map featuresnot Syft
  • A stormwater utility recording CCTV sewer inspection results against pipe segments for regulatory reportingnot Syft
  • A transport agency modelling pavement treatment strategies to defend a road resurfacing budgetnot Syft
  • A city consolidating sign, signal and streetlight inventories that currently live in separate spreadsheetsnot Syft

Where each one falls short

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.

VUEWorks

  • The product assumes a maintained enterprise ArcGIS geodatabase; agencies without one face a spatial data cleanup project before VUEWorks does anything useful, and that project is usually quoted by the same consultancy selling the software.
  • No pricing is published and deals are typically bundled with consulting services, which makes it hard to separate the software cost from the data work when comparing bids.
  • The interface is functional rather than modern, and field crews accustomed to consumer mobile apps often resist it, which undermines the data quality the capital planning depends on.
  • The Esri dependency is also an Esri cost: agencies need current ArcGIS Enterprise or ArcGIS Online licensing, and that sits outside the VUEWorks quote entirely.
  • It is a small vendor with a limited partner network and a mainly North American footprint, so support and implementation capacity outside that region is thin.

Pricing, plan by plan

Syft

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

VUEWorks

On request
  • VUEWorks Enterprise$undefined/year
    • Quoted per agency by user count and modules
    • Hosted or on-premise deployment options
    • GIS integration, data migration and configuration quoted separately

Which should you pick?

Choose Syft if

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

Choose VUEWorks if

  • You need native esri integration.
  • You work on Web, iOS, Android.
  • You also want work orders and requests.
VUEWorks review

Questions people ask

Is Syft or VUEWorks better?
Neither clearly leads. Syft starts at Free and VUEWorks at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Syft or VUEWorks?
Syft has a free tier; the other does not. Paid plans start at Free for Syft and On request for VUEWorks.
Does Syft or VUEWorks run on more platforms?
Syft runs on macOS, Linux, Windows, Docker. VUEWorks runs on Web, iOS, Android.
Can I use Syft for free?
Yes. Syft has a free tier, so you can try it without paying. VUEWorks starts at On request.
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 VUEWorks is typically brought in for.
What can Syft do that VUEWorks cannot?
Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations. VUEWorks covers Native Esri integration, Work orders and requests, Inspections, Condition and risk.

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.

VUEWorks: Do we need Esri ArcGIS?

Effectively yes. The asset register is the GIS, and the ArcGIS licensing sits outside the VUEWorks quote.

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.

VUEWorks: Is pricing published?

No. VUEWorks is quoted per agency by users and modules, often bundled with data collection services.

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.

VUEWorks: Can it replace Cityworks?

It occupies the same GIS-centric municipal asset management space, so yes in principle, but migration means remapping workflows and history.

Syft: What does Anchore Enterprise cost?

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

VUEWorks: Is there a cloud option?

Yes, VUEWorks is offered hosted as well as on-premise.

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

More on Syft

More on VUEWorks

Keep looking

Other head to heads