syft

Generate SBOMs from container images and filesystems

anchore/syft · SBOM Generation · scanned v1.55.0 (released 2026-10-19) · commit f15c3343e29d · last scan 2026-11-02

The scan method changed on 2026-11-02. npm development dependencies and npm-shrinkwrap.json are now scanned; matches on GitHub Actions referenced by a moving tag and on npm packages the repository defines itself are no longer counted; directories such as integration-tests and test-fixtures are excluded as fixtures. Most differences from the previous week below come from that change, not from the projects. Details.

Changes since last week

27 removed; 45 resolved.

Removed (27)

github.com/davecgh/go-spew@v1.1.1, github.com/fsnotify/fsnotify@v1.8.0, github.com/go-viper/mapstructure/v2@v2.2.1, github.com/pelletier/go-toml/v2@v2.2.3, github.com/pmezard/go-difflib@v1.0.0, github.com/sagikazarmark/locafero@v0.7.0, github.com/sirupsen/logrus@v1.9.3, github.com/sourcegraph/conc@v0.3.0, github.com/spf13/afero@v1.12.0, github.com/spf13/cast@v1.7.1, github.com/spf13/pflag@v1.0.6, github.com/spf13/viper@v1.20.1, github.com/stretchr/testify@v1.10.0, go.uber.org/multierr@v1.10.0, go.uber.org/zap@v1.27.0, golang.org/x/sys@v0.33.0, golang.org/x/text@v0.21.0, gopkg.in/yaml.v3@v3.0.1, @img/sharp-darwin-arm64@0.33.5, @img/sharp-linux-x64@0.33.5, axios@1.6.0, color@4.2.3, follow-redirects@1.15.3, ghostty-web@github:rcarmo/ghostty-web#6c1c75b, lodash@4.17.21, sharp@0.33.5, tracestrings@github:oven-sh/bun.report#912ca63

Resolved advisories (45)

• M GHSA-2464-8j7c-4cjm in github.com/go-viper/mapstructure/v2@v2.2.1
• H GHSA-35jp-ww65-95wh in axios@1.6.0
• H GHSA-3g43-6gmg-66jw in axios@1.6.0
• M GHSA-3p68-rc4w-qgx5 in axios@1.6.0
• M GHSA-3w6x-2g7m-8v23 in axios@1.6.0
• M GHSA-42h9-826w-cgv3 in axios@1.6.0
• H GHSA-43fc-jf86-j433 in axios@1.6.0
• M GHSA-445q-vr5w-6q77 in axios@1.6.0
• H GHSA-4hjh-wcwx-xvwj in axios@1.6.0
• M GHSA-5c9x-8gcm-mpgx in axios@1.6.0
• M GHSA-62hf-57xw-28j9 in axios@1.6.0
• H GHSA-6chq-wfr3-2hj9 in axios@1.6.0
• M GHSA-7q8q-rj6j-mhjq in axios@1.6.0
• M GHSA-898c-q2cr-xwhg in axios@1.6.0
• H GHSA-8hc4-vh64-cxmj in axios@1.6.0
• M GHSA-9fr6-4gfg-395g in axios@1.6.0
• M GHSA-cxjh-pqwp-8mfp in follow-redirects@1.15.3
• M GHSA-f23m-r3pf-42rh in lodash@4.17.21
• H GHSA-f88m-g3jw-g9cj in sharp@0.33.5
• M GHSA-fv92-fjc5-jj9h in github.com/go-viper/mapstructure/v2@v2.2.1
• M GHSA-fvcv-3m26-pcqx in axios@1.6.0
• H GHSA-hfxv-24rg-xrqf in axios@1.6.0
• H GHSA-j5f8-grm9-p9fc in axios@1.6.0
• M GHSA-j8rh-479h-cp32 in axios@1.6.0
• M GHSA-jchw-25xp-jwwc in follow-redirects@1.15.3
• H GHSA-jr5f-v2jv-69x6 in axios@1.6.0
• M GHSA-m7pr-hjqh-92cm in axios@1.6.0
• M GHSA-mmx7-hfxf-jppx in axios@1.6.0
• H GHSA-p92q-9vqr-4j8v in axios@1.6.0
• H GHSA-pf86-5x62-jrwf in axios@1.6.0
• M GHSA-pmv8-rq9r-6j72 in axios@1.6.0
• H GHSA-pmwg-cvhr-8vh7 in axios@1.6.0
• H GHSA-q8qp-cvcw-x6jj in axios@1.6.0
• M GHSA-r4q5-vmmm-2653 in follow-redirects@1.15.3
• H GHSA-r5fr-rjxr-66jc in lodash@4.17.21
• H GHSA-rgj7-g3m4-5g8c in sharp@0.33.5
• M GHSA-vf2m-468p-8v99 in axios@1.6.0
• M GHSA-w9j2-pvgh-6h63 in axios@1.6.0
• H GHSA-wq5f-xc86-pv6w in sharp@0.33.5
• L GHSA-xhjh-pmcv-23jw in axios@1.6.0
• M GHSA-xx6v-rp6x-q39c in axios@1.6.0
• M GHSA-xxjr-mmjv-4gpg in lodash@4.17.21
• L GO-2026-5024 in golang.org/x/sys@v0.33.0
• H GO-2026-5970 in golang.org/x/text@v0.21.0
• H GO-2026-6629 in golang.org/x/text@v0.21.0

Known vulnerabilities (4)

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. OSV: also reported by OSV-Scanner. Released binary: for Go tools, whether govulncheck found the vulnerable code in the shipped Linux binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Select an advisory for every catalog tool it matches. If a match is wrong or does not apply, use Dispute; accepted disputes are annotated here and listed on the corrections page, and the match stays visible.

Second opinion: OSV-Scanner

OSV-Scanner found 4 advisories in the same files; 4 of Grype's matches are confirmed by it (marked ✓ above). 0 advisories were reported only by OSV-Scanner.

Vulnerable code in the released binary

govulncheck analyzed syft from syft_1.55.0_linux_amd64.tar.gz, built with go1.26.8. 16 advisories have vulnerable functions compiled into it: 13 in the Go standard library and 3 in dependencies.

Of the 4 Go advisories Grype matched in the source, 1 are in modules or code paths that are not in the shipped binary.

The Go linker removes unreachable functions, so a vulnerable function in the binary is likely reachable. Standard-library advisories are fixed by rebuilding with a newer Go release.

Release integrity

Verdict: verified for syft_1.55.0_linux_amd64.tar.gz. The download matches GitHub's recorded digest.

• Checksums file: yes
• Signatures: yes
• SLSA provenance: no
• SBOM published with the release: yes

Verified means a signature, provenance, or attestation was checked against an identity in anchore/syft's own GitHub Actions workflows.

Repository security (OpenSSF Scorecard)

Score 8.7/10, assessed 2026-10-26 (OpenSSF public dataset). Scorecard viewer

GitHub Actions workflow audit (zizmor)

8 potential issues in 5 workflow files at this release: 0 high, 0 medium, 8 low severity (medium or high confidence only). Each is a pattern to review, not a confirmed vulnerability.

Dependencies (355)

By ecosystem: golang 339, github 15, unknown 1.

Licenses (as declared in the SBOM): unknown 355.

History

SBOM minimum elements

Scored by sbomlyze on the generated source SBOM. A source SBOM usually lacks supplier and hash data, so these scores mostly reflect what the project's manifests declare.

Evidence

Downloads for this week: CycloneDX SBOM · Grype report · sbomlyze diff from last week

Permanent copy of the raw SBOM, Grype, OSV-Scanner, and govulncheck output and release checks: release report-2026-11-02, folder supply-chain-shard-*/anchore__syft/.

Full JSON for this project · Atom feed of weekly changes

Badges

shields.io endpoints refreshed with each weekly scan. They report this week's result for the latest release, nothing more.

[![release verification](https://img.shields.io/endpoint?url=https%3A%2F%2Frezmoss.github.io%2Fawesome-security-pipeline%2Fbadges%2Fanchore%2Fsyft%2Frelease.json)](https://rezmoss.github.io/awesome-security-pipeline/projects/anchore/syft/index.html)
[![vulnerable code in binary](https://img.shields.io/endpoint?url=https%3A%2F%2Frezmoss.github.io%2Fawesome-security-pipeline%2Fbadges%2Fanchore%2Fsyft%2Fin-binary.json)](https://rezmoss.github.io/awesome-security-pipeline/projects/anchore/syft/index.html)

How this report is made

Every Sunday a GitHub Actions workflow resolves each catalog tool to its latest release and runs the checks below. Every tool is installed from its own latest release and verified against its published checksum or digest. Nothing from the scanned projects is built or executed; release binaries are analyzed as files.