Release archive
3.2.57

CRYPTO-SECURITY-PROVENANCE-COVERAGE (Audit Source Visibility)

Release v3.2.57 focuses on CRYPTO-SECURITY-PROVENANCE-COVERAGE (Audit Source Visibility).

FixedInternal
CRYPTO-SECURITY-PROVENANCE-COVERAGE (Audit Source Visibility)

Release digest

Fixed

  • CRYPTO-SECURITY-PROVENANCE-COVERAGE (Audit Source Visibility) — Crypto project headers now show every attached security provenance source instead of only the first one, so assets such as LayerZero can surface both Dropstab and Official Audits when the API provides both sources.

Internal

  • Added frontend runtime-contract coverage to keep crypto security provenance from being truncated back to one source.
  • Verified the targeted frontend runtime-contract tests locally.
  • Verified frontend lint and the dashboard production build locally.
  • Smoke-tested the local /app/crypto/layerzero preview with mocked security sources and confirmed both Security: Dropstab and Security: Official Audits render without a project-not-found state.
  • Updated release notes for the production-visible crypto security provenance fix. No knowledge-base update is required because this only clarifies an authenticated dashboard source-display behavior and does not introduce public setup, API, or legal guidance.

Technical notes