Issues

hdf convert: --max-size cannot lift the 50 MiB converter input cap (43 converters hard-code it), and convert output already exceeds validate's default

#334

· clem-field opened

on Sep 13, 2026

hdf → oscal-sar: a baseline with no controls emits an empty control-selection that fails OSCAL 1.2.x (still present in 3.6.0-rc.5)

#333

· clem-field opened

on Sep 12, 2026

hdf-amendments → oscal-poam: empty requirementId emits empty titles that fail OSCAL 1.2.x, and the emitters are tested against 1.1.2 only

#331

· clem-field opened

on Sep 12, 2026

hdf convert: InSpec exec-json with an object-valued results[].resource_id fails to parse — 2% of results block 100% of the document

#328

· clem-field opened

on Sep 11, 2026

v2 ⇄ v3 fidelity: components[] dropped on downgrade with no passthrough carrier and only a generic warning, while amendments got both

#325

· clem-field opened

on Sep 11, 2026

Prisma Cloud CSPM has no conversion path — both existing converters target Compute (and is the 'prisma-to-hdf' label misleading?)

#324

· clem-field opened

on Sep 10, 2026

hdf fetch: pull the GitLab Vulnerability Report (with triage state) and iterate a group, not just one job artifact

#323

· clem-field opened

on Sep 10, 2026

`hdf list --detail` help text advertises `interconnections`, a value the parser rejects — the field was renamed to `dataFlows` and the help never followed

#284

· clem-field opened

on Sep 5, 2026

checkov-to-hdf: every finding is tagged SA-11/RA-5 — port the 1341-entry check-to-control mapping that hdf-converters 2.14.0 already ships

#279

· clem-field opened

on Sep 4, 2026

amend apply silently no-ops on HDF v2 (InSpec exec-json) results — the shape @mitre/saf converters emit

#248

· clem-field opened

on Aug 25, 2026

Checkov JUnit XML routes to junit-to-hdf and silently loses its metadata

#241

· clem-field opened

on Aug 23, 2026

Derive NIST 800-53 Rev 5 mappings from check text, with scored 1:n candidates and 3PAO adjudication

#239

· clem-field opened

on Aug 22, 2026

Navigation Menu

Uh oh!

All issues

hdf convert: --max-size cannot lift the 50 MiB converter input cap (43 converters hard-code it), and convert output already exceeds validate's default

hdf → oscal-sar: a baseline with no controls emits an empty control-selection that fails OSCAL 1.2.x (still present in 3.6.0-rc.5)

hdf-amendments → oscal-poam: empty requirementId emits empty titles that fail OSCAL 1.2.x, and the emitters are tested against 1.1.2 only

hdf convert: InSpec exec-json with an object-valued results[].resource_id fails to parse — 2% of results block 100% of the document

v2 ⇄ v3 fidelity: components[] dropped on downgrade with no passthrough carrier and only a generic warning, while amendments got both

Prisma Cloud CSPM has no conversion path — both existing converters target Compute (and is the 'prisma-to-hdf' label misleading?)

hdf fetch: pull the GitLab Vulnerability Report (with triage state) and iterate a group, not just one job artifact

`hdf list --detail` help text advertises `interconnections`, a value the parser rejects — the field was renamed to `dataFlows` and the help never followed

checkov-to-hdf: every finding is tagged SA-11/RA-5 — port the 1341-entry check-to-control mapping that hdf-converters 2.14.0 already ships

amend apply silently no-ops on HDF v2 (InSpec exec-json) results — the shape @mitre/saf converters emit

Checkov JUnit XML routes to junit-to-hdf and silently loses its metadata

Derive NIST 800-53 Rev 5 mappings from check text, with scored 1:n candidates and 3PAO adjudication

Uh oh!

Search results