CRYPTO-SECURITY-EVIDENCE-ALIAS-NORMALIZATION (Report Logic)

Release digest

CRYPTO-SECURITY-EVIDENCE-ALIAS-NORMALIZATION (Report Logic) — Crypto project normalization now derives security_evidence from common audit aliases such as audits, audit_reports, security.audit_reports, and single audit-report URL fields. Reports can now treat aliased audit labels, providers, scopes, dates, and remediation status as attached security evidence without rendering raw audit URLs or raw covered-contract addresses.

Added backend normalizer, PDF view-model, and rendered-PDF coverage for aliased security evidence inputs, including raw URL/address suppression and removal of false Security evidence depth backlog rows when detailed evidence is already attached.
Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md because this changes security evidence-state behavior. Public-docs decision: user-facing crypto docs now explain audit-alias normalization as provenance context only, not a formal smart contract audit, safety claim, verified-truth claim, legal conclusion, or investment advice.