Const ExperimentalThe specific algorithm used to create the cryptographic hash value is not defined. In situations where an artifact has multiple cryptographic hashes, it is up to the implementer to choose which hash value to set here; this should be the most secure hash algorithm that is suitable for the situation and consistent with the corresponding attestation. The implementer can then provide the other hash values through an additional set of attribute extensions as they deem necessary.
This attribute is experimental and is subject to breaking changes in minor releases of @opentelemetry/semantic-conventions.
The full hash value (see glossary), often found in checksum.txt on a release of the artifact and used to verify package integrity.