Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note. After verifying the
signature, provenance_bytes can be unmarshalled and compared to the
provenance to confirm that it is unchanged. A base64-encoded string
representation of the provenance bytes is used for the signature in order
to interoperate with openssl which expects this format for signature
verification.
The serialized form is captured both to avoid ambiguity in how the
provenance is marshalled to json as well to prevent incompatibilities with
future changes.
Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note. After verifying the
signature, provenance_bytes can be unmarshalled and compared to the
provenance to confirm that it is unchanged. A base64-encoded string
representation of the provenance bytes is used for the signature in order
to interoperate with openssl which expects this format for signature
verification.
The serialized form is captured both to avoid ambiguity in how the
provenance is marshalled to json as well to prevent incompatibilities with
future changes.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[]]
