Your SBOM never leaves your machine.

FDA's premarket cybersecurity guidance asks for thirteen things about your software bill of materials. ceproof checks your component list against all thirteen for free, and fills in the ones a tool can honestly fill in — a level of support and an end-of-support date per component, a CISA Known Exploited Vulnerabilities screen, the dependency graph carried through from your own SBOM — then names every remaining gap out loud. There is no network call at any point: no upload, no telemetry, no licence check over the wire. Your device's component list stays inside your network.

npx ceproof scan --profile fda --sbom firmware.cdx.json

The moment this tool exists for

The submission is being assembled and someone asks for the SBOM. You have one — your build produces it. What you do not have is a level of support and an end-of-support date for each of 400 components, a record of which of them appear in CISA's exploited-vulnerability catalogue, and a document that says which of those questions you could not answer and why. That is the part that gets assembled by hand, in a spreadsheet, under deadline, and then goes stale the next time firmware ships.

What the guidance actually asks for

Section V.A.4(b) of FDA's Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (issued 3 February 2026) asks manufacturers to provide machine-readable SBOMs consistent with the NTIA minimum elements, and then adds, per software component:

“The software level of support provided through monitoring and maintenance from the software component manufacturer (e.g., the software is actively maintained, no longer maintained, abandoned); and the software component's end-of-support date.”

And, for vulnerabilities: “manufacturers should also identify all known vulnerabilities associated with the device and the software components, including those identified in CISA's Known Exploited Vulnerabilities Catalog. For each known vulnerability, manufacturers should describe how the vulnerabilities were discovered…”

Then, for components with known vulnerabilities: “A safety and security risk assessment of each known vulnerability (including device and system impacts); and details of applicable safety and security risk controls to address the vulnerability.”

ceproof produces the first two, screens for the third, and leaves the last two for you — because they are the two things the guidance asks you for, and no component scanner can answer them. Every item it checks is cited to that text, and every citation is verified against the guidance verbatim by a test in the source.

The NTIA minimum elements it cites are NTIA, The Minimum Elements For a Software Bill of Materials (SBOM), published 12 July 2021 under Executive Order 14028. The free template page sets out all seven of them, with what each one actually means for a firmware component.

How it works

1

Point it at your SBOM

--sbom firmware.cdx.json imports CycloneDX JSON (spec 1.4–1.6), detected from the file's own contents. Device firmware is usually C/C++ and has no lockfile to scan, so ceproof starts where your build leaves off. Ship a Node or Python companion app too? It scans that and merges both — additive, never competing, with each component recording its origin.

2

See where you stand on all thirteen, free

scan --profile fda checks your component list against every SBOM content item in the guidance and reports each as DERIVED, PARTIAL or NEEDS-HUMAN-INPUT, with the counts that make it concrete: how many components have a level of support, how many have an end-of-support date, how many KEV findings, how many open items. Free, forever, no key. In CI it is report-only by default — it exits 0 and reports, because three of the thirteen items can only ever be answered by a human, so it never turns a build red on its own. Gate the build on it deliberately with --fail-on partial when you want that.

3

Generate the pack

report --format fda-pack writes seven files: the enriched CycloneDX 1.6 SBOM, the support and end-of-support addendum, the vulnerability table with the two columns you fill in, the summary, the open-items list, the provenance record and the disclaimer. Offline, reproducible, stamped with the catalogue version it was screened against.

What you get

FileWhat it is
fda-sbom.cyclonedx.jsonThe enriched CycloneDX 1.6 SBOM. Level of support and end-of-support date as namespaced properties, your source SBOM's dependency graph carried through verbatim, and the screen's findings as an explicitly unassessed vulnerability array.
fda-support-eol.csvOne row per component: identifiers, origin, level of support, end-of-support date, and the basis for each value.
fda-vulnerabilities.csvOne row per finding, including the ones screened out, with the two columns you fill in. The working copy.
fda-summary.mdThe document a human reads: scope, method, component inventory, the two per-component values, the vulnerability table, the open items, the provenance.
fda-open-items.mdEverything still needing a person, split into what no tool can supply and what you must check on what it did supply — with the action for each.
fda-provenance.jsonWhat produced the pack, from which inputs (by SHA-256), against which datasets, under which licences, on what date.
DISCLAIMER.mdThe standing disclaimer as its own file, naming which artifacts state it inline and which cannot.

The thirteen-item view is the free part, and stays free. The pack is the documentation that answers what it can of those items; it does not reprint the checklist back at you.

Honest scope

ceproof does not make your submission acceptable to FDA, and no tool can. It is a documentation generator. Nothing it produces has been reviewed or endorsed by FDA or by CISA, and it supports your own review of your submission rather than replacing it.

It screens; you assess. The safety and security risk assessment of each vulnerability, and the risk controls you apply, are the two things the guidance asks the manufacturer for. They read NEEDS-HUMAN-INPUT in every artifact until you write them, and nothing in the output ever implies otherwise.

The vulnerability screen covers the CISA KEV catalogue only — the subset FDA names explicitly. FDA asks for all known vulnerabilities; identify the rest by other means and carry them into the same table. This is one input to that list, not the whole of it.

A C/C++ component can only ever reach “possible”. A version-precise match needs an npm or PyPI advisory with affected version ranges, and no equivalent data is bundled for C/C++. The output says that, per row, rather than letting you discover it later.

A level of support is a commitment, not an observable fact. Where no public dataset answers it, ceproof says unknown and states why — it never derives “abandoned” and never invents an end-of-support date. Declare the real value yourself and it travels through as manufacturer-declared, outranking everything derived.

Dependency relationships are carried through, never inferred. If your source SBOM has no dependency graph, or only top-level edges, the pack says so rather than letting the absence pass for an assertion that there are none.

CycloneDX JSON in, for now. SPDX import is not implemented in this version and is refused with a message saying so, rather than half-parsed.

No network call, ever. No telemetry, no upload, no licence check over the wire. It runs inside your network, against data bundled in the package, and the source has a test that enforces that file by file.

Pricing

Free, forever

The full thirteen-item view — scan --profile fda across every SBOM content item, your SBOM imported and merged, the KEV screen, the counts, JSON output and CI exit codes (report-only by default). No account, no telemetry, no network calls.

Included with the CLI

Company

$499 per year

Unlocks the documentation pack for your own devices: the enriched SBOM, the support and end-of-support addendum, the vulnerability table, the summary, the open-items list and the provenance record. Regenerate it as often as you ship.

Buy

Consultant

$1,499 per year

Everything in Company, licensed for client work — generate packs for unlimited client devices. Same artifacts, same offline guarantee.

Buy

The FDA tiers are annual subscriptions, and a fresh key is emailed to you each year when the subscription renews. The key states the date it runs until; when the year is up the tool tells you the subscription needs renewing and names the date — it is never reported as an invalid key, every artifact you have already generated is yours to keep, and the free thirteen-item view keeps working either way. Sign in at https://billing.stripe.com/p/login/3cI9AUdldbQN0o22kb6oo00 with the email you bought with to cancel or update your card.

Questions

Does this make my submission acceptable to FDA?

No, and no tool can. ceproof assembles and structures SBOM documentation against the content items the guidance asks for, with every item cited to the guidance text. What you submit, and whether it is adequate, is yours and FDA's.

My firmware is C and C++. Can this scan it?

No. ceproof does not scan C or C++ source, does not run a compiler, and does not parse Yocto, Buildroot, Conan or CMake trees. It starts from the SBOM you already have. If you also ship a Node or Python companion app, it scans that and merges both into one component list.

Which SBOM formats can I import?

CycloneDX JSON, spec versions 1.4, 1.5 and 1.6, detected from the file's own contents rather than its extension. syft, cdxgen and Trivy all emit a supported format. SPDX import is not implemented in this version and is refused with a message that says so, rather than half-parsed.

Does it find all my vulnerabilities?

No. It screens the CISA Known Exploited Vulnerabilities Catalog, which is the subset FDA names explicitly. The rest you identify by other means and carry into the same table. The output states that limit on every artifact that carries a finding.

Does it assess the vulnerabilities it finds?

No, deliberately. The risk assessment and the risk controls are the two things the guidance asks the manufacturer for, and both need knowledge of your device that no component scanner has. They read NEEDS-HUMAN-INPUT until you write them.

Does my device data leave our network?

No. There is no network call at any point. Every lookup resolves against data bundled inside the package, and a test in the source enforces that per file.

How current is the vulnerability data?

The KEV catalogue and the end-of-support data are snapshots bundled with each release, and each document states the catalogue version and release date it was screened against. Once either is more than 30 days old, every artifact carries a visible warning.

Is this legal or regulatory advice?

No. It is a documentation generator. Have the output reviewed by whoever owns regulatory affairs for your device.