Engineering notes

Blog

How bomwerk builds software inventories you can hand to an auditor, and the trade-offs behind them. No hype, concrete numbers, limitations stated.

  • Your CI Clone Has No Submodules. Your SBOM Should Still Know Their Versions.

    A default CI checkout leaves git submodules empty, so a scanner sees a folder name and no version. bomwerk now reads the pinned commit straight from the git index, and the SBOM carries it.

  • PHP2Shell Is Now Officially Exploited. Your First Hour as a Manufacturer.

    CISA added both PHP2Shell flaws to its Known Exploited Vulnerabilities catalogue on 26 October. If a PHP engine ships inside your product, here is the order of work for the first hour, and where bomwerk fits.

  • One Source Tree, Two Builds, Two Answers: What the 90-Second Video Shows

    A static scan sees the same files for every build configuration. bomwerk's observe and trim ask the compiler what each build used. Here is the committed result on our open test repo, and where it stops.

  • PHP2Shell Is a Version Question. Here's What a Scan Answers Today, and What It Doesn't.

    Two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, were patched on 21 October after details leaked. If PHP ships inside your product, the first job is knowing which version. We ran bomwerk 1.0.0-rc.1 against four ways PHP ends up in a product and report what it found, including what it missed.

  • How We Keep the Paid Code Out of the Open Repo, and How You Can Check

    bomwerk's core is Apache-2.0. The paid extension is a separate private repository. What stops one from leaking into the other, which two checks run on every change, and the one command you can run yourself to audit the public history.

  • The Nightmare Repo Has Real Numbers. Now You Can Check Them Yourself.

    bomwerk/nightmare has carried a ground-truth benchmark against syft, cdxgen, and sbom-tool for weeks. Until now, bomwerk's own row couldn't be independently reproduced. The open-source core plus the v1.0.0-rc.1 tag change that. Here are the numbers, what they don't prove, and the exact commands to run them yourself.

  • bomwerk Is Open Source Now. Here's Exactly What That Means.

    The scanner's core, parsers, heuristics, build-evidence tooling, and vulnerability matching are public today at github.com/bomwerk/bomwerk under Apache-2.0. What you can actually do with that today, what's still commercial and still in preview, and why there's a public adversarial test repo you're invited to try to break it with.

  • Four Feeds, But Only One Starts the Clock

    OSV, NVD, CISA KEV, ENISA EUVD: bomwerk's own materials list all four as vulnerability sources, which makes it sound like some kind of weighted-voting merge happens behind the scenes. It doesn't. Each feed answers a different question, one of them isn't wired up yet, and only one of them is what actually triggers the CRA's 24-hour clock.