Expand description
JSON report writer for NIST submission.
NIST MPTS consumes machine-readable JSON: one entry per vector run,
each carrying the scheme identity, pass/fail outcome, message and
byte tallies, round count, and elapsed time. The harness produces
raw measurements only — Confium does not score or rank; NIST decides
what the numbers mean (see 09-nist-evaluation-harness.md:
“Anti-goals”).
Report is a thin typed wrapper over a Vec<ReportEntry>; call
Report::to_json for the string NIST expects, or
Report::to_json_pretty for a human-friendly variant.
Structs§
- Report
- A batch of vector results, serializable as the JSON NIST ingests.
- Report
Entry - One row in the output report.