Thanks, @Matthew_Read.
I understand that these metadata fields aren’t directly tied to the digital signature or protected attributes. However, it’s worth noting that earlier versions of the binaries did include these fields — such as product name, version, and copyright — which made it easier to verify authenticity and track builds, especially in offline or controlled environments.
While I agree it’s not a strict security requirement, having that metadata adds transparency, improves traceability across releases, and helps teams performing audits or version checks to quickly validate binaries.
It would be great if future builds could restore this metadata for consistency with previous versions and to maintain trust in offline or compliance-sensitive setups.