Portability: 4 stdlib scripts, no network. Fill CSVs, run, keep the output with the software file.
Not a conformity assessment. IEC 62304 is paywalled: clause markers here come from two agreeing secondary sources (🟡) and your licensed copy prevails. A notified body or FDA reviewer can read a borderline call differently.
Software files fail review in the same places: a class claimed lower than the
harm allows, an "external" risk control that lives in the same software system,
a SOUP list with "latest" as the version and no anomaly review, a trace matrix
with risk controls nobody tested, and security treated as an afterthought.
Three classifications get confused, and they use different inputs:
| Question | Decided by | Assessed |
|---|---|---|
| IEC 62304 class A/B/C (which activities) | worst-case harm, clause 4.3 + A1 Fig. 3 | after risk controls external to the software system |
| FDA Basic / Enhanced (what you submit) | probable risk of death or serious injury | before any risk controls |
| FD&C Act 524B cyber device | software + any internet-capable path (USB counts) | not risk-based |
# 1 - Classify: system and item classes, FDA level, cyber device?
python scripts/software_safety_classifier.py --inventory assets/software_inventory.example.csv
# 2 - Gap check: is every activity the class requires done, with evidence?
python scripts/lifecycle_gap_check.py --class B --security --assessment assets/lifecycle_assessment.example.csv
# 3 - SOUP: identified, specified, anomaly lists reviewed, in the SBOM?
python scripts/soup_register_check.py --register assets/soup_register.example.csv --sbom assets/sbom.example.cdx.json --cyber-device
# 4 - Release: every requirement tested, every risk control verified?
python scripts/trace_matrix_check.py --matrix assets/trace_matrix.example.csv --class C --release
Class first: steps 2 to 4 take the class from step 1. --template prints an
empty input; lifecycle_gap_check.py --list --class X prints the required ids.
--release, any untested requirement or open failed result without an anomaly record (5.7, 5.8).| Script | Role | Exit codes |
|---|---|---|
scripts/software_safety_classifier.py | 62304 4.3 class per system and item, segregation, FDA documentation level, 524B cyber device | 0 classified · 2 findings · 3 bad input · 4 blocked |
scripts/lifecycle_gap_check.py | 62304 activities by class (+4.4 legacy), 81001-5-1 activities with --security | 0 ready · 2 gaps · 3 · 4 blocked |
scripts/soup_register_check.py | 8.1.2, 5.3.3/5.3.4, 7.1.3, end of support, 81001-5-1 risk-transfer category, SBOM cross-check (CycloneDX/SPDX) | 0 pass · 2 · 3 · 4 blocked |
scripts/trace_matrix_check.py | system → software requirement → test → result, risk control → hazard, release state | 0 pass · 2 · 3 · 4 blocked |
All support --help, --sample, --template and --output json.
references/classification_and_documentation_levels.md — 62304 class decision path, external controls, segregation, FDA Basic/Enhanced, 524B, EU status, Edition 2 (10 sources)references/lifecycle_requirements_by_class.md — every clause by class, legacy software, regulatory standing (7 sources)references/secure_lifecycle_81001_5_1.md — 81001-5-1 clause map, ISH1:2025 risk transfer, mapping to 524B and MDCG 2019-16 (7 sources)references/soup_and_traceability.md — SOUP evidence by class, SBOM, what reviewers check in a trace matrix (8 sources)assets/*.example.csv, assets/sbom.example.cdx.json — input formats, generated from each script's --sample