Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. After verifying the signature,provenance_bytescan 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.
In-toto Statement representation as defined in spec. The intoto_statement can contain any type of provenance. The serialized payload of the statement can be stored and signed in the Occurrence's envelope.
In-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa spec, wrapped in an in-toto statement. This allows for direct jsonification of a to-spec in-toto slsa statement with a to-spec slsa provenance.
Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note. After verifying the
signature,provenance_bytescan 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.
Returns
Type
Description
string
setProvenanceBytes
Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note. After verifying the
signature,provenance_bytescan 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.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getIntotoProvenance
Deprecated. See InTotoStatement for the replacement.
In-toto Provenance representation as defined in spec.
In-toto Statement representation as defined in spec.
The intoto_statement can contain any type of provenance. The serialized
payload of the statement can be stored and signed in the Occurrence's
envelope.
In-toto Statement representation as defined in spec.
The intoto_statement can contain any type of provenance. The serialized
payload of the statement can be stored and signed in the Occurrence's
envelope.
In-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa
spec, wrapped in an in-toto statement. This allows for direct
jsonification of a to-spec in-toto slsa statement with a to-spec
slsa provenance.
In-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa
spec, wrapped in an in-toto statement. This allows for direct
jsonification of a to-spec in-toto slsa statement with a to-spec
slsa provenance.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Grafeas V1 Client - Class BuildOccurrence (1.2.2)\n\nVersion latestkeyboard_arrow_down\n\n- [1.2.2 (latest)](/php/docs/reference/grafeas/latest/V1.BuildOccurrence)\n- [1.2.1](/php/docs/reference/grafeas/1.2.1/V1.BuildOccurrence)\n- [1.1.3](/php/docs/reference/grafeas/1.1.3/V1.BuildOccurrence)\n- [1.0.0](/php/docs/reference/grafeas/1.0.0/V1.BuildOccurrence)\n- [0.10.3](/php/docs/reference/grafeas/0.10.3/V1.BuildOccurrence)\n- [0.9.0](/php/docs/reference/grafeas/0.9.0/V1.BuildOccurrence)\n- [0.8.3](/php/docs/reference/grafeas/0.8.3/V1.BuildOccurrence)\n- [0.7.1](/php/docs/reference/grafeas/0.7.1/V1.BuildOccurrence)\n- [0.6.0](/php/docs/reference/grafeas/0.6.0/V1.BuildOccurrence)\n- [0.5.0](/php/docs/reference/grafeas/0.5.0/V1.BuildOccurrence)\n- [0.4.4](/php/docs/reference/grafeas/0.4.4/V1.BuildOccurrence) \nReference documentation and code samples for the Grafeas V1 Client class BuildOccurrence.\n\nDetails of a build occurrence.\n\nGenerated from protobuf message `grafeas.v1.BuildOccurrence`\n\nNamespace\n---------\n\nGrafeas \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getProvenance\n\nThe actual provenance for the build.\n\n### hasProvenance\n\n### clearProvenance\n\n### setProvenance\n\nThe actual provenance for the build.\n\n### getProvenanceBytes\n\nSerialized JSON representation of the provenance, used in generating the\nbuild signature in the corresponding build note. After verifying the\nsignature, `provenance_bytes` can be unmarshalled and compared to the\nprovenance to confirm that it is unchanged. A base64-encoded string\nrepresentation of the provenance bytes is used for the signature in order\nto interoperate with openssl which expects this format for signature\nverification.\n\nThe serialized form is captured both to avoid ambiguity in how the\nprovenance is marshalled to json as well to prevent incompatibilities with\nfuture changes.\n\n### setProvenanceBytes\n\nSerialized JSON representation of the provenance, used in generating the\nbuild signature in the corresponding build note. After verifying the\nsignature, `provenance_bytes` can be unmarshalled and compared to the\nprovenance to confirm that it is unchanged. A base64-encoded string\nrepresentation of the provenance bytes is used for the signature in order\nto interoperate with openssl which expects this format for signature\nverification.\n\nThe serialized form is captured both to avoid ambiguity in how the\nprovenance is marshalled to json as well to prevent incompatibilities with\nfuture changes.\n\n### getIntotoProvenance\n\nDeprecated. See InTotoStatement for the replacement.\n\nIn-toto Provenance representation as defined in spec.\n\n### hasIntotoProvenance\n\n### clearIntotoProvenance\n\n### setIntotoProvenance\n\nDeprecated. See InTotoStatement for the replacement.\n\nIn-toto Provenance representation as defined in spec.\n\n### getIntotoStatement\n\nIn-toto Statement representation as defined in spec.\n\nThe intoto_statement can contain any type of provenance. The serialized\npayload of the statement can be stored and signed in the Occurrence's\nenvelope.\n\n### hasIntotoStatement\n\n### clearIntotoStatement\n\n### setIntotoStatement\n\nIn-toto Statement representation as defined in spec.\n\nThe intoto_statement can contain any type of provenance. The serialized\npayload of the statement can be stored and signed in the Occurrence's\nenvelope.\n\n### getInTotoSlsaProvenanceV1\n\nIn-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa\nspec, wrapped in an in-toto statement. This allows for direct\njsonification of a to-spec in-toto slsa statement with a to-spec\nslsa provenance.\n\n### hasInTotoSlsaProvenanceV1\n\n### clearInTotoSlsaProvenanceV1\n\n### setInTotoSlsaProvenanceV1\n\nIn-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa\nspec, wrapped in an in-toto statement. This allows for direct\njsonification of a to-spec in-toto slsa statement with a to-spec\nslsa provenance."]]
