Release archive
3.2.197

CRYPTO-SECURITY-ASSESSMENT-EVIDENCE-ALIASES (Report Logic)

Release v3.2.197 focuses on CRYPTO-SECURITY-ASSESSMENT-EVIDENCE-ALIASES (Report Logic).

FixedInternal
CRYPTO-SECURITY-ASSESSMENT-EVIDENCE-ALIASES (Report Logic)

Release digest

Fixed

  • CRYPTO-SECURITY-ASSESSMENT-EVIDENCE-ALIASES (Report Logic) — Crypto project normalization now recognizes security-assessment and finding-count payload shapes such as security_assessments, security.assessments, assessment_title, vendor, assessor, findings, issue_count, resolved_findings, unresolved_findings, reviewed_at, assessed_at, report_link, remediation_state, and fix_status.

Internal

  • Added focused coverage proving assessment/finding payloads normalize into reviewer-safe security_evidence rows with label, provider, safe finding-count scope, date, remediation, and URL context while keeping raw finding text out of PDF-facing view-model rows.
  • Updated docs/architecture/CRYPTO_REPORTS.md and docs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.md because this expands the internal security-evidence normalization contract. Public docs decision: no public documentation change is required because this only expands accepted attached evidence shapes and does not change downloadable PDF behavior, billing, audit coverage, safety language, legal claims, or investment guidance.

Technical notes