--- title: "POST /v1/{+parent}/occurrences:batchCreate" method: POST path: "/v1/{+parent}/occurrences:batchCreate" tags: ["projects"] --- # POST /v1/{+parent}/occurrences:batchCreate `POST /v1/{+parent}/occurrences:batchCreate` Creates new occurrences in batch. ## Path parameters - `parent` string, required ## Request body - BatchCreateOccurrencesRequest — Request to create occurrences in batch. - `occurrences` Occurrence[] — Required. The occurrences to create. Max allowed length is 1000. - `createTime` string, google-datetime — Output only. The time this occurrence was created. - `compliance` ComplianceOccurrence — An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason. - `version` ComplianceVersion — Describes the CIS benchmark version that is applicable to a given OS and os version. - `cpeUri` string — The CPE URI (https://cpe.mitre.org/specification/) this benchmark is applicable to. - `version` string — The version of the benchmark. This is set to the version of the OS-specific CIS document the benchmark is defined in. - `benchmarkDocument` string — The name of the document that defines this benchmark, e.g. "CIS Container-Optimized OS". - `nonCompliantFiles` NonCompliantFile[] - `displayCommand` string — Command to display the non-compliant files. - `path` string — Empty if `display_command` is set. - `reason` string — Explains why a file is non compliant for a CIS check. - `nonComplianceReason` string - `dsseAttestation` DSSEAttestationOccurrence — Deprecated. Prefer to use a regular Occurrence, and populate the Envelope at the top level of the Occurrence. - `envelope` Envelope — MUST match https://github.com/secure-systems-lab/dsse/blob/master/envelope.proto. An authenticated message of arbitrary type. - `signatures` EnvelopeSignature[] - `sig` string, byte - `keyid` string - `payloadType` string - `payload` string, byte - `statement` InTotoStatement — Spec defined at https://github.com/in-toto/attestation/tree/main/spec#statement The serialized InTotoStatement will be stored as Envelope.payload. Envelope.payloadType is always "application/vnd.in-toto+json". - `slsaProvenance` SlsaProvenance - `builder` SlsaBuilder - `id` string - `recipe` SlsaRecipe — Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe. - `definedInMaterial` string, int64 — Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64. - `entryPoint` string — String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use. - `arguments` object — Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Depending on the recipe Type, the structure may be different. - `environment` object — Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Depending on the recipe Type, the structure may be different. - `type` string — URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials. - `materials` Material[] — The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty. - `uri` string - `digest` object - `metadata` SlsaMetadata — Other properties of the build. - `buildInvocationId` string — Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec. - `buildStartedOn` string, google-datetime — The timestamp of when the build started. - `reproducible` boolean — If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output. - `buildFinishedOn` string, google-datetime — The timestamp of when the build completed. - `completeness` SlsaCompleteness — Indicates that the builder claims certain fields in this message to be complete. - … - `provenance` InTotoProvenance - `recipe` Recipe — Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe. - `type` string — URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials. - `arguments` object[] — Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Since the arguments field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - … - `environment` object[] — Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Since the environment field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - … - `definedInMaterial` string, int64 — Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64. - `entryPoint` string — String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use. - `materials` string[] — The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty. - `metadata` Metadata — Other properties of the build. - `buildInvocationId` string — Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec. - `buildStartedOn` string, google-datetime — The timestamp of when the build started. - `reproducible` boolean — If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output. - `buildFinishedOn` string, google-datetime — The timestamp of when the build completed. - `completeness` Completeness — Indicates that the builder claims certain fields in this message to be complete. - … - `builderConfig` BuilderConfig - `id` string - `_type` string — Always `https://in-toto.io/Statement/v0.1`. - `subject` Subject[] - `name` string - `digest` object — `"": ""` Algorithms can be e.g. sha256, sha512 See https://github.com/in-toto/attestation/blob/main/spec/field_types.md#DigestSet - `predicateType` string — `https://slsa.dev/provenance/v0.1` for SlsaProvenance. - `slsaProvenanceZeroTwo` SlsaProvenanceZeroTwo — See full explanation of fields at slsa.dev/provenance/v0.2. - `materials` GrafeasV1SlsaProvenanceZeroTwoSlsaMaterial[] - `digest` object - `uri` string - `metadata` GrafeasV1SlsaProvenanceZeroTwoSlsaMetadata — Other properties of the build. - `buildInvocationId` string - `buildStartedOn` string, google-datetime - `reproducible` boolean - `buildFinishedOn` string, google-datetime - `completeness` GrafeasV1SlsaProvenanceZeroTwoSlsaCompleteness — Indicates that the builder claims certain fields in this message to be complete. - … - `builder` GrafeasV1SlsaProvenanceZeroTwoSlsaBuilder — Identifies the entity that executed the recipe, which is trusted to have correctly performed the operation and populated this provenance. - `id` string - `invocation` GrafeasV1SlsaProvenanceZeroTwoSlsaInvocation — Identifies the event that kicked off the build. - `environment` object - `configSource` GrafeasV1SlsaProvenanceZeroTwoSlsaConfigSource — Describes where the config file that kicked off the build came from. This is effectively a pointer to the source where buildConfig came from. - … - `parameters` object - `buildConfig` object - `buildType` string - `image` ImageOccurrence — Details of the derived image portion of the DockerImage relationship. This image would be produced from a Dockerfile with FROM . - `fingerprint` Fingerprint — A set of properties that uniquely identify a given Docker image. - `v2Name` string — Output only. The name of the image's v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + " " + v2_name[N+1]) Only the name of the final blob is kept. - `v2Blob` string[] — Required. The ordered list of v2 blobs that represent a given image. - `v1Name` string — Required. The layer ID of the final layer in the Docker image's v1 representation. - `distance` integer — Output only. The number of layers by which this image differs from the associated image basis. - `layerInfo` Layer[] — This contains layer-specific metadata, if populated it has length "distance" and is ordered with [distance] being the layer immediately following the base image and [1] being the final layer. - `arguments` string — The recovered arguments to the Dockerfile directive. - `directive` string — Required. The recovered Dockerfile directive used to construct this layer. See https://docs.docker.com/engine/reference/builder/ for more information. - `baseResourceUrl` string — Output only. This contains the base image URL for the derived image occurrence. - `discovery` DiscoveryOccurrence — Provides information about the analysis status of a discovered resource. - `analysisCompleted` AnalysisCompleted — Indicates which analysis completed successfully. Multiple types of analysis can be performed on a single resource. - `analysisType` string[] - `sbomStatus` SBOMStatus — The status of an SBOM generation. - `sbomState` 'SBOM_STATE_UNSPECIFIED' | 'PENDING' | 'COMPLETE' — The progress of the SBOM generation. - `error` string — If there was an error generating an SBOM, this will indicate what that error was. - `continuousAnalysis` 'CONTINUOUS_ANALYSIS_UNSPECIFIED' | 'ACTIVE' | 'INACTIVE' — Whether the resource is continuously analyzed. - `analysisStatus` 'ANALYSIS_STATUS_UNSPECIFIED' | 'PENDING' | 'SCANNING' | 'FINISHED_SUCCESS' | 'COMPLETE' | 'FINISHED_FAILED' | 'FINISHED_UNSUPPORTED' — The status of discovery for the resource. - `analysisStatusError` Status — The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). - `code` integer — The status code, which should be an enum value of google.rpc.Code. - `message` string — A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client. - `details` object[] — A list of messages that carry the error details. There is a common set of message types for APIs to use. - `lastScanTime` string, google-datetime — The last time this resource was scanned. - `analysisError` Status[] — Indicates any errors encountered during analysis of a resource. There could be 0 or more of these errors. - `code` integer — The status code, which should be an enum value of google.rpc.Code. - `message` string — A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client. - `details` object[] — A list of messages that carry the error details. There is a common set of message types for APIs to use. - `cpe` string — The CPE of the resource being scanned. - `archiveTime` string, google-datetime — Output only. The time occurrences related to this discovery occurrence were archived. - `files` File[] — Files that make up the resource described by the occurrence. - `name` string - `digest` object - `lastVulnerabilityUpdateTime` string, google-datetime — The last time vulnerability scan results changed. - `upgrade` UpgradeOccurrence — An Upgrade Occurrence represents that a specific resource_url could install a specific upgrade. This presence is supplied via local sources (i.e. it is present in the mirror and the running system has noticed its availability). For Windows, both distribution and windows_update contain information for the Windows update. - `package` string — Required for non-Windows OS. The package this Upgrade is for. - `parsedVersion` Version — Version contains structured information about the version of a package. - `kind` 'VERSION_KIND_UNSPECIFIED' | 'NORMAL' | 'MINIMUM' | 'MAXIMUM' — Required. Distinguishes between sentinel MIN/MAX versions and normal versions. - `revision` string — The iteration of the package build from the above version. - `epoch` integer — Used to correct mistakes in the version numbering scheme. - `fullName` string — Human readable version string. This string is of the form :- and is only set when kind is NORMAL. - `name` string — Required only when version kind is NORMAL. The main part of the version name. - `inclusive` boolean — Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range. - `distribution` UpgradeDistribution — The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities. - `severity` string — The severity as specified by the upstream operating system. - `cve` string[] — The cve tied to this Upgrade. - `cpeUri` string — Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/. - `classification` string — The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed. For Windows the classification is one of the category_ids listed at https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ff357803(v=vs.85) - `windowsUpdate` WindowsUpdate — Windows Update represents the metadata about the update for the Windows operating system. The fields in this message come from the Windows Update API documented at https://docs.microsoft.com/en-us/windows/win32/api/wuapi/nn-wuapi-iupdate. - `title` string — The localized title of the update. - `supportUrl` string — The hyperlink to the support information for the update. - `identity` Identity — The unique identifier of the update. - `revision` integer — The revision number of the update. - `updateId` string — The revision independent identifier of the update. - `description` string — The localized description of the update. - `kbArticleIds` string[] — The Microsoft Knowledge Base article IDs that are associated with the update. - `lastPublishedTimestamp` string, google-datetime — The last published timestamp of the update. - `categories` Category[] — The list of categories to which the update belongs. - `categoryId` string — The identifier of the category. - `name` string — The localized name of the category. - `sbomReference` SBOMReferenceOccurrence — The occurrence representing an SBOM reference as applied to a specific resource. The occurrence follows the DSSE specification. See https://github.com/secure-systems-lab/dsse/blob/master/envelope.md for more details. - `signatures` EnvelopeSignature[] — The signatures over the payload. - `sig` string, byte - `keyid` string - `payloadType` string — The kind of payload that SbomReferenceIntotoPayload takes. Since it's in the intoto format, this value is expected to be 'application/vnd.in-toto+json'. - `payload` SbomReferenceIntotoPayload — The actual payload that contains the SBOM Reference data. The payload follows the intoto statement specification. See https://github.com/in-toto/attestation/blob/main/spec/v1.0/statement.md for more details. - `subject` Subject[] — Set of software artifacts that the attestation applies to. Each element represents a single software artifact. - `name` string - `digest` object — `"": ""` Algorithms can be e.g. sha256, sha512 See https://github.com/in-toto/attestation/blob/main/spec/field_types.md#DigestSet - `predicate` SbomReferenceIntotoPredicate — A predicate which describes the SBOM being referenced. - `location` string — The location of the SBOM. - `mimeType` string — The mime type of the SBOM. - `referrerId` string — The person or system referring this predicate to the consumer. - `digest` object — A map of algorithm to digest of the contents of the SBOM. - `_type` string — Identifier for the schema of the Statement. - `predicateType` string — URI identifying the type of the Predicate. - `advisoryPublishTime` string, google-datetime — The time this advisory was published by the source. - `build` BuildOccurrence — Details of a build occurrence. - `provenanceBytes` string — 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. - `provenance` BuildProvenance — Provenance of a build. Contains all information needed to verify the full details about the build from source to completion. - `projectId` string — ID of the project. - `startTime` string, google-datetime — Time at which execution of the build was started. - `id` string — Required. Unique identifier of the build. - `commands` Command[] — Commands requested by the build. - `name` string — Required. Name of the command, as presented on the command line, or if the command is packaged as a Docker container, as presented to `docker pull`. - `dir` string — Working directory (relative to project source root) used when running this command. - `args` string[] — Command-line arguments used when executing this command. - `env` string[] — Environment variables set before running this command. - `id` string — Optional unique identifier for this command, used in wait_for to reference this command as a dependency. - `waitFor` string[] — The ID(s) of the command(s) that this command depends on. - `triggerId` string — Trigger identifier if the build was triggered automatically; empty if not. - `creator` string — E-mail address of the user who initiated this build. Note that this was the user's e-mail address at the time the build was initiated; this address may not represent the same end-user for all time. - `buildOptions` object — Special options applied to this build. This is a catch-all field where build providers can enter any desired additional details. - `endTime` string, google-datetime — Time at which execution of the build was finished. - `createTime` string, google-datetime — Time at which the build was created. - `logsUri` string — URI where any logs for this provenance were written. - `sourceProvenance` Source — Source describes the location of the source used for the build. - `context` SourceContext — A SourceContext is a reference to a tree of files. A SourceContext together with a path point to a unique revision of a single file or directory. - `cloudRepo` CloudRepoSourceContext — A CloudRepoSourceContext denotes a particular revision in a Google Cloud Source Repo. - … - `gerrit` GerritSourceContext — A SourceContext referring to a Gerrit project. - … - `labels` object — Labels with user defined metadata. - `git` GitSourceContext — A GitSourceContext denotes a particular revision in a third party Git repository (e.g., GitHub). - … - `fileHashes` object — Hash(es) of the build source, which can be used to verify that the original source integrity was maintained in the build. The keys to this map are file paths used as build source and the values contain the hash values for those files. If the build source came in a single package such as a gzipped tarfile (.tar.gz), the FileHash will be for the single path to that file. - `artifactStorageSourceUri` string — If provided, the input binary artifacts for the build came from this location. - `additionalContexts` SourceContext[] — If provided, some of the source code used for the build may be found in these locations, in the case where the source repository had multiple remotes or submodules. This list will not include the context specified in the context field. - `cloudRepo` CloudRepoSourceContext — A CloudRepoSourceContext denotes a particular revision in a Google Cloud Source Repo. - … - `gerrit` GerritSourceContext — A SourceContext referring to a Gerrit project. - … - `labels` object — Labels with user defined metadata. - `git` GitSourceContext — A GitSourceContext denotes a particular revision in a third party Git repository (e.g., GitHub). - … - `builderVersion` string — Version string of the builder at the time this build was executed. - `builtArtifacts` Artifact[] — Output of the build. - `id` string — Artifact ID, if any; for container images, this will be a URL by digest like `gcr.io/projectID/imagename@sha256:123456`. - `names` string[] — Related artifact names. This may be the path to a binary or jar file, or in the case of a container build, the name used to push the container image to Google Container Registry, as presented to `docker push`. Note that a single Artifact ID can have multiple names, for example if two tags are applied to one image. - `checksum` string — Hash or checksum value of a binary, or Docker Registry 2.0 digest of a container. - `intotoProvenance` InTotoProvenance - `recipe` Recipe — Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe. - `type` string — URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials. - `arguments` object[] — Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Since the arguments field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - `environment` object[] — Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Since the environment field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - `definedInMaterial` string, int64 — Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64. - `entryPoint` string — String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use. - `materials` string[] — The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty. - `metadata` Metadata — Other properties of the build. - `buildInvocationId` string — Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec. - `buildStartedOn` string, google-datetime — The timestamp of when the build started. - `reproducible` boolean — If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output. - `buildFinishedOn` string, google-datetime — The timestamp of when the build completed. - `completeness` Completeness — Indicates that the builder claims certain fields in this message to be complete. - `arguments` boolean — If true, the builder claims that recipe.arguments is complete, meaning that all external inputs are properly captured in the recipe. - `environment` boolean — If true, the builder claims that recipe.environment is claimed to be complete. - `materials` boolean — If true, the builder claims that materials are complete, usually through some controls to prevent network access. Sometimes called "hermetic". - `builderConfig` BuilderConfig - `id` string - `intotoStatement` InTotoStatement — Spec defined at https://github.com/in-toto/attestation/tree/main/spec#statement The serialized InTotoStatement will be stored as Envelope.payload. Envelope.payloadType is always "application/vnd.in-toto+json". - `slsaProvenance` SlsaProvenance - `builder` SlsaBuilder - `id` string - `recipe` SlsaRecipe — Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe. - `definedInMaterial` string, int64 — Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64. - `entryPoint` string — String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use. - `arguments` object — Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Depending on the recipe Type, the structure may be different. - `environment` object — Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Depending on the recipe Type, the structure may be different. - `type` string — URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials. - `materials` Material[] — The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty. - `uri` string - `digest` object - `metadata` SlsaMetadata — Other properties of the build. - `buildInvocationId` string — Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec. - `buildStartedOn` string, google-datetime — The timestamp of when the build started. - `reproducible` boolean — If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output. - `buildFinishedOn` string, google-datetime — The timestamp of when the build completed. - `completeness` SlsaCompleteness — Indicates that the builder claims certain fields in this message to be complete. - … - `provenance` InTotoProvenance - `recipe` Recipe — Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe. - `type` string — URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials. - `arguments` object[] — Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Since the arguments field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - … - `environment` object[] — Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Since the environment field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any". - … - `definedInMaterial` string, int64 — Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64. - `entryPoint` string — String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use. - `materials` string[] — The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty. - `metadata` Metadata — Other properties of the build. - `buildInvocationId` string — Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec. - `buildStartedOn` string, google-datetime — The timestamp of when the build started. - `reproducible` boolean — If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output. - `buildFinishedOn` string, google-datetime — The timestamp of when the build completed. - `completeness` Completeness — Indicates that the builder claims certain fields in this message to be complete. - … - `builderConfig` BuilderConfig - `id` string - `_type` string — Always `https://in-toto.io/Statement/v0.1`. - `subject` Subject[] - `name` string - `digest` object — `"": ""` Algorithms can be e.g. sha256, sha512 See https://github.com/in-toto/attestation/blob/main/spec/field_types.md#DigestSet - `predicateType` string — `https://slsa.dev/provenance/v0.1` for SlsaProvenance. - `slsaProvenanceZeroTwo` SlsaProvenanceZeroTwo — See full explanation of fields at slsa.dev/provenance/v0.2. - `materials` GrafeasV1SlsaProvenanceZeroTwoSlsaMaterial[] - `digest` object - `uri` string - `metadata` GrafeasV1SlsaProvenanceZeroTwoSlsaMetadata — Other properties of the build. - `buildInvocationId` string - `buildStartedOn` string, google-datetime - `reproducible` boolean - `buildFinishedOn` string, google-datetime - `completeness` GrafeasV1SlsaProvenanceZeroTwoSlsaCompleteness — Indicates that the builder claims certain fields in this message to be complete. - … - `builder` GrafeasV1SlsaProvenanceZeroTwoSlsaBuilder — Identifies the entity that executed the recipe, which is trusted to have correctly performed the operation and populated this provenance. - `id` string - `invocation` GrafeasV1SlsaProvenanceZeroTwoSlsaInvocation — Identifies the event that kicked off the build. - `environment` object - `configSource` GrafeasV1SlsaProvenanceZeroTwoSlsaConfigSource — Describes where the config file that kicked off the build came from. This is effectively a pointer to the source where buildConfig came from. - … - `parameters` object - `buildConfig` object - `buildType` string - `inTotoSlsaProvenanceV1` InTotoSlsaProvenanceV1 - `subject` Subject[] - `name` string - `digest` object — `"": ""` Algorithms can be e.g. sha256, sha512 See https://github.com/in-toto/attestation/blob/main/spec/field_types.md#DigestSet - `predicate` SlsaProvenanceV1 — Keep in sync with schema at https://github.com/slsa-framework/slsa/blob/main/docs/provenance/schema/v1/provenance.proto Builder renamed to ProvenanceBuilder because of Java conflicts. - `buildDefinition` BuildDefinition - `externalParameters` object - `resolvedDependencies` ResourceDescriptor[] - … - `buildType` string - `internalParameters` object - `runDetails` RunDetails - `builder` ProvenanceBuilder - … - `byproducts` ResourceDescriptor[] - … - `metadata` BuildMetadata - … - `_type` string — InToto spec defined at https://github.com/in-toto/attestation/tree/main/spec#statement - `predicateType` string - `updateTime` string, google-datetime — Output only. The time this occurrence was last updated. - `resourceUri` string — Required. Immutable. A URI that represents the resource for which the occurrence applies. For example, `https://gcr.io/project/image@sha256:123abc` for a Docker image. - `vulnerability` VulnerabilityOccurrence — An occurrence of a severity vulnerability on a resource. - `vexAssessment` VexAssessment — VexAssessment provides all publisher provided Vex information that is related to this vulnerability. - `vulnerabilityId` string — The vulnerability identifier for this Assessment. Will hold one of common identifiers e.g. CVE, GHSA etc. - `remediations` Remediation[] — Specifies details on how to handle (and presumably, fix) a vulnerability. - `details` string — Contains a comprehensive human-readable discussion of the remediation. - `remediationType` 'REMEDIATION_TYPE_UNSPECIFIED' | 'MITIGATION' | 'NO_FIX_PLANNED' | 'NONE_AVAILABLE' | 'VENDOR_FIX' | 'WORKAROUND' — The type of remediation that can be applied. - `remediationUri` RelatedUrl — Metadata for any related URL information. - `url` string — Specific URL associated with the resource. - `label` string — Label to describe usage of the URL. - `justification` Justification — Justification provides the justification when the state of the assessment if NOT_AFFECTED. - `justificationType` 'JUSTIFICATION_TYPE_UNSPECIFIED' | 'COMPONENT_NOT_PRESENT' | 'VULNERABLE_CODE_NOT_PRESENT' | 'VULNERABLE_CODE_NOT_IN_EXECUTE_PATH' | 'VULNERABLE_CODE_CANNOT_BE_CONTROLLED_BY_ADVERSARY' | 'INLINE_MITIGATIONS_ALREADY_EXIST' — The justification type for this vulnerability. - `details` string — Additional details on why this justification was chosen. - `noteName` string — The VulnerabilityAssessment note from which this VexAssessment was generated. This will be of the form: `projects/[PROJECT_ID]/notes/[NOTE_ID]`. - `cve` string — Holds the MITRE standard Common Vulnerabilities and Exposures (CVE) tracking number for the vulnerability. Deprecated: Use vulnerability_id instead to denote CVEs. - `relatedUris` RelatedUrl[] — Holds a list of references associated with this vulnerability item and assessment. - `url` string — Specific URL associated with the resource. - `label` string — Label to describe usage of the URL. - `impacts` string[] — Contains information about the impact of this vulnerability, this will change with time. - `state` 'STATE_UNSPECIFIED' | 'AFFECTED' | 'NOT_AFFECTED' | 'FIXED' | 'UNDER_INVESTIGATION' — Provides the state of this Vulnerability assessment. - `type` string — The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.). - `cvssVersion` 'CVSS_VERSION_UNSPECIFIED' | 'CVSS_VERSION_2' | 'CVSS_VERSION_3' | 'CVSS_VERSION_4' — Output only. CVSS version used to populate cvss_score and severity. - `severity` 'SEVERITY_UNSPECIFIED' | 'MINIMAL' | 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL' — Output only. The note provider assigned severity of this vulnerability. - `fixAvailable` boolean — Output only. Whether at least one of the affected packages has a fix available. - `risk` Risk - `epss` ExploitPredictionScoringSystem - `percentile` number, double — The percentile of the current score, the proportion of all scored vulnerabilities with the same or a lower EPSS score - `score` number, double — The EPSS score representing the probability [0-1] of exploitation in the wild in the next 30 days - `cisaKev` CISAKnownExploitedVulnerabilities - `knownRansomwareCampaignUse` string — Whether the vulnerability is known to have been leveraged as part of a ransomware campaign. - `cvssV4` CVSS — Common Vulnerability Scoring System. For details, see https://www.first.org/cvss/specification-document This is a message we will try to use for storing various versions of CVSS rather than making a separate proto for storing a specific version. - `userInteraction` 'USER_INTERACTION_UNSPECIFIED' | 'USER_INTERACTION_NONE' | 'USER_INTERACTION_REQUIRED' | 'USER_INTERACTION_PASSIVE' | 'USER_INTERACTION_ACTIVE' — User Interaction (UI). Defined in CVSS v3, v4. - `impactScore` number, float - `vulnerableSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Availability Impact (VA). Defined in CVSS v4. - `authentication` 'AUTHENTICATION_UNSPECIFIED' | 'AUTHENTICATION_MULTIPLE' | 'AUTHENTICATION_SINGLE' | 'AUTHENTICATION_NONE' — Authentication (Au). Defined in CVSS v2. - `exploitMaturity` 'EXPLOIT_MATURITY_UNSPECIFIED' | 'EXPLOIT_MATURITY_NOT_DEFINED' | 'EXPLOIT_MATURITY_ATTACKED' | 'EXPLOIT_MATURITY_POC' | 'EXPLOIT_MATURITY_UNREPORTED' — Exploit Maturity (E). Defined in CVSS v4. - `subsequentSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Integrity Impact (SI). Defined in CVSS v4. - `integrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Integrity Impact (I). Defined in CVSS v2, v3. - `attackRequirements` 'ATTACK_REQUIREMENTS_UNSPECIFIED' | 'ATTACK_REQUIREMENTS_NONE' | 'ATTACK_REQUIREMENTS_PRESENT' — Attack Requirements (AT). Defined in CVSS v4. - `exploitabilityScore` number, float - `attackComplexity` 'ATTACK_COMPLEXITY_UNSPECIFIED' | 'ATTACK_COMPLEXITY_LOW' | 'ATTACK_COMPLEXITY_HIGH' | 'ATTACK_COMPLEXITY_MEDIUM' — Attack Complexity (AC). Defined in CVSS v2, v3, v4. - `availabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Availability Impact (A). Defined in CVSS v2, v3. - `privilegesRequired` 'PRIVILEGES_REQUIRED_UNSPECIFIED' | 'PRIVILEGES_REQUIRED_NONE' | 'PRIVILEGES_REQUIRED_LOW' | 'PRIVILEGES_REQUIRED_HIGH' — Privileges Required (PR). Defined in CVSS v3, v4. - `baseScore` number, float — The base score is a function of the base metric scores. - `vulnerableSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Confidentiality Impact (VC). Defined in CVSS v4. - `vulnerableSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Integrity Impact (VI). Defined in CVSS v4. - `subsequentSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Confidentiality Impact (SC). Defined in CVSS v4. - `subsequentSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Availability Impact (SA). Defined in CVSS v4. - `scope` 'SCOPE_UNSPECIFIED' | 'SCOPE_UNCHANGED' | 'SCOPE_CHANGED' — Scope (S). Defined in CVSS v3. - `confidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Confidentiality Impact (C). Defined in CVSS v2, v3. - `attackVector` 'ATTACK_VECTOR_UNSPECIFIED' | 'ATTACK_VECTOR_NETWORK' | 'ATTACK_VECTOR_ADJACENT' | 'ATTACK_VECTOR_LOCAL' | 'ATTACK_VECTOR_PHYSICAL' — Attack Vector (AV). Defined in CVSS v2, v3, v4. - `packageIssue` PackageIssue[] — Required. The set of affected locations and their fixes (if available) within the associated resource. - `packageType` string — The type of package (e.g. OS, MAVEN, GO). - `effectiveSeverity` 'SEVERITY_UNSPECIFIED' | 'MINIMAL' | 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL' — Output only. The distro or language system assigned severity for this vulnerability when that is available and note provider assigned severity when it is not available. - `fixedVersion` Version — Version contains structured information about the version of a package. - `kind` 'VERSION_KIND_UNSPECIFIED' | 'NORMAL' | 'MINIMUM' | 'MAXIMUM' — Required. Distinguishes between sentinel MIN/MAX versions and normal versions. - `revision` string — The iteration of the package build from the above version. - `epoch` integer — Used to correct mistakes in the version numbering scheme. - `fullName` string — Human readable version string. This string is of the form :- and is only set when kind is NORMAL. - `name` string — Required only when version kind is NORMAL. The main part of the version name. - `inclusive` boolean — Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range. - `affectedVersion` Version — Version contains structured information about the version of a package. - `kind` 'VERSION_KIND_UNSPECIFIED' | 'NORMAL' | 'MINIMUM' | 'MAXIMUM' — Required. Distinguishes between sentinel MIN/MAX versions and normal versions. - `revision` string — The iteration of the package build from the above version. - `epoch` integer — Used to correct mistakes in the version numbering scheme. - `fullName` string — Human readable version string. This string is of the form :- and is only set when kind is NORMAL. - `name` string — Required only when version kind is NORMAL. The main part of the version name. - `inclusive` boolean — Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range. - `fixAvailable` boolean — Output only. Whether a fix is available for this package. - `fileLocation` GrafeasV1FileLocation[] — The location at which this package was found. - `layerDetails` LayerDetails — Details about the layer a package was found in. - `chainId` string — The layer chain ID (sha256 hash) of the layer in the container image. https://github.com/opencontainers/image-spec/blob/main/config.md#layer-chainid - `diffId` string — The diff ID (typically a sha256 hash) of the layer in the container image. - `index` integer — The index of the layer in the container image. - `command` string — The layer build command that was used to build the layer. This may not be found in all layers depending on how the container image is built. - `baseImages` BaseImage[] — The base images the layer is found within. - … - `filePath` string — For jars that are contained inside .war files, this filepath can indicate the path to war file combined with the path to jar file. - `lineNumber` integer — Line number in the file where the package was found. Optional field that only applies to source repository scanning. - `affectedPackage` string — Required. The package this vulnerability was found in. - `fixedCpeUri` string — The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability was fixed in. It is possible for this to be different from the affected_cpe_uri. - `affectedCpeUri` string — Required. The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability was found in. - `fixedPackage` string — The package this vulnerability was fixed in. It is possible for this to be different from the affected_package. - `longDescription` string — Output only. A detailed description of this vulnerability. - `extraDetails` string — Occurrence-specific extra details about the vulnerability. - `relatedUrls` RelatedUrl[] — Output only. URLs related to this vulnerability. - `url` string — Specific URL associated with the resource. - `label` string — Label to describe usage of the URL. - `effectiveSeverity` 'SEVERITY_UNSPECIFIED' | 'MINIMAL' | 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL' — The distro assigned severity for this vulnerability when it is available, otherwise this is the note provider assigned severity. When there are multiple PackageIssues for this vulnerability, they can have different effective severities because some might be provided by the distro while others are provided by the language ecosystem for a language pack. For this reason, it is advised to use the effective severity on the PackageIssue level. In the case where multiple PackageIssues have differing effective severities, this field should be the highest severity for any of the PackageIssues. - `cvssv3` CVSS — Common Vulnerability Scoring System. For details, see https://www.first.org/cvss/specification-document This is a message we will try to use for storing various versions of CVSS rather than making a separate proto for storing a specific version. - `userInteraction` 'USER_INTERACTION_UNSPECIFIED' | 'USER_INTERACTION_NONE' | 'USER_INTERACTION_REQUIRED' | 'USER_INTERACTION_PASSIVE' | 'USER_INTERACTION_ACTIVE' — User Interaction (UI). Defined in CVSS v3, v4. - `impactScore` number, float - `vulnerableSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Availability Impact (VA). Defined in CVSS v4. - `authentication` 'AUTHENTICATION_UNSPECIFIED' | 'AUTHENTICATION_MULTIPLE' | 'AUTHENTICATION_SINGLE' | 'AUTHENTICATION_NONE' — Authentication (Au). Defined in CVSS v2. - `exploitMaturity` 'EXPLOIT_MATURITY_UNSPECIFIED' | 'EXPLOIT_MATURITY_NOT_DEFINED' | 'EXPLOIT_MATURITY_ATTACKED' | 'EXPLOIT_MATURITY_POC' | 'EXPLOIT_MATURITY_UNREPORTED' — Exploit Maturity (E). Defined in CVSS v4. - `subsequentSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Integrity Impact (SI). Defined in CVSS v4. - `integrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Integrity Impact (I). Defined in CVSS v2, v3. - `attackRequirements` 'ATTACK_REQUIREMENTS_UNSPECIFIED' | 'ATTACK_REQUIREMENTS_NONE' | 'ATTACK_REQUIREMENTS_PRESENT' — Attack Requirements (AT). Defined in CVSS v4. - `exploitabilityScore` number, float - `attackComplexity` 'ATTACK_COMPLEXITY_UNSPECIFIED' | 'ATTACK_COMPLEXITY_LOW' | 'ATTACK_COMPLEXITY_HIGH' | 'ATTACK_COMPLEXITY_MEDIUM' — Attack Complexity (AC). Defined in CVSS v2, v3, v4. - `availabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Availability Impact (A). Defined in CVSS v2, v3. - `privilegesRequired` 'PRIVILEGES_REQUIRED_UNSPECIFIED' | 'PRIVILEGES_REQUIRED_NONE' | 'PRIVILEGES_REQUIRED_LOW' | 'PRIVILEGES_REQUIRED_HIGH' — Privileges Required (PR). Defined in CVSS v3, v4. - `baseScore` number, float — The base score is a function of the base metric scores. - `vulnerableSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Confidentiality Impact (VC). Defined in CVSS v4. - `vulnerableSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Integrity Impact (VI). Defined in CVSS v4. - `subsequentSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Confidentiality Impact (SC). Defined in CVSS v4. - `subsequentSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Availability Impact (SA). Defined in CVSS v4. - `scope` 'SCOPE_UNSPECIFIED' | 'SCOPE_UNCHANGED' | 'SCOPE_CHANGED' — Scope (S). Defined in CVSS v3. - `confidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Confidentiality Impact (C). Defined in CVSS v2, v3. - `attackVector` 'ATTACK_VECTOR_UNSPECIFIED' | 'ATTACK_VECTOR_NETWORK' | 'ATTACK_VECTOR_ADJACENT' | 'ATTACK_VECTOR_LOCAL' | 'ATTACK_VECTOR_PHYSICAL' — Attack Vector (AV). Defined in CVSS v2, v3, v4. - `cvssV2` CVSS — Common Vulnerability Scoring System. For details, see https://www.first.org/cvss/specification-document This is a message we will try to use for storing various versions of CVSS rather than making a separate proto for storing a specific version. - `userInteraction` 'USER_INTERACTION_UNSPECIFIED' | 'USER_INTERACTION_NONE' | 'USER_INTERACTION_REQUIRED' | 'USER_INTERACTION_PASSIVE' | 'USER_INTERACTION_ACTIVE' — User Interaction (UI). Defined in CVSS v3, v4. - `impactScore` number, float - `vulnerableSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Availability Impact (VA). Defined in CVSS v4. - `authentication` 'AUTHENTICATION_UNSPECIFIED' | 'AUTHENTICATION_MULTIPLE' | 'AUTHENTICATION_SINGLE' | 'AUTHENTICATION_NONE' — Authentication (Au). Defined in CVSS v2. - `exploitMaturity` 'EXPLOIT_MATURITY_UNSPECIFIED' | 'EXPLOIT_MATURITY_NOT_DEFINED' | 'EXPLOIT_MATURITY_ATTACKED' | 'EXPLOIT_MATURITY_POC' | 'EXPLOIT_MATURITY_UNREPORTED' — Exploit Maturity (E). Defined in CVSS v4. - `subsequentSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Integrity Impact (SI). Defined in CVSS v4. - `integrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Integrity Impact (I). Defined in CVSS v2, v3. - `attackRequirements` 'ATTACK_REQUIREMENTS_UNSPECIFIED' | 'ATTACK_REQUIREMENTS_NONE' | 'ATTACK_REQUIREMENTS_PRESENT' — Attack Requirements (AT). Defined in CVSS v4. - `exploitabilityScore` number, float - `attackComplexity` 'ATTACK_COMPLEXITY_UNSPECIFIED' | 'ATTACK_COMPLEXITY_LOW' | 'ATTACK_COMPLEXITY_HIGH' | 'ATTACK_COMPLEXITY_MEDIUM' — Attack Complexity (AC). Defined in CVSS v2, v3, v4. - `availabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Availability Impact (A). Defined in CVSS v2, v3. - `privilegesRequired` 'PRIVILEGES_REQUIRED_UNSPECIFIED' | 'PRIVILEGES_REQUIRED_NONE' | 'PRIVILEGES_REQUIRED_LOW' | 'PRIVILEGES_REQUIRED_HIGH' — Privileges Required (PR). Defined in CVSS v3, v4. - `baseScore` number, float — The base score is a function of the base metric scores. - `vulnerableSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Confidentiality Impact (VC). Defined in CVSS v4. - `vulnerableSystemIntegrityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Vulnerable System Integrity Impact (VI). Defined in CVSS v4. - `subsequentSystemConfidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Confidentiality Impact (SC). Defined in CVSS v4. - `subsequentSystemAvailabilityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Subsequent System Availability Impact (SA). Defined in CVSS v4. - `scope` 'SCOPE_UNSPECIFIED' | 'SCOPE_UNCHANGED' | 'SCOPE_CHANGED' — Scope (S). Defined in CVSS v3. - `confidentialityImpact` 'IMPACT_UNSPECIFIED' | 'IMPACT_HIGH' | 'IMPACT_LOW' | 'IMPACT_NONE' | 'IMPACT_PARTIAL' | 'IMPACT_COMPLETE' — Confidentiality Impact (C). Defined in CVSS v2, v3. - `attackVector` 'ATTACK_VECTOR_UNSPECIFIED' | 'ATTACK_VECTOR_NETWORK' | 'ATTACK_VECTOR_ADJACENT' | 'ATTACK_VECTOR_LOCAL' | 'ATTACK_VECTOR_PHYSICAL' — Attack Vector (AV). Defined in CVSS v2, v3, v4. - `shortDescription` string — Output only. A one sentence description of this vulnerability. - `cvssScore` number, float — Output only. The CVSS score of this vulnerability. CVSS score is on a scale of 0 - 10 where 0 indicates low severity and 10 indicates high severity. - `deployment` DeploymentOccurrence — The period during which some deployable was active in a runtime. - `undeployTime` string, google-datetime — End of the lifetime of this deployment. - `deployTime` string, google-datetime — Required. Beginning of the lifetime of this deployment. - `config` string — Configuration used to create this deployment. - `address` string — Address of the runtime element hosting this deployment. - `resourceUri` string[] — Output only. Resource URI for the artifact being deployed taken from the deployable field with the same name. - `userEmail` string — Identity of the user that triggered this deployment. - `platform` 'PLATFORM_UNSPECIFIED' | 'GKE' | 'FLEX' | 'CUSTOM' — Platform hosting this deployment. - `aiSkillAnalysis` AISkillAnalysisOccurrence — AISkillAnalysisOccurrence provides the results of an AI-based skill analysis. - `maxSeverity` 'SEVERITY_UNSPECIFIED' | 'CRITICAL' | 'HIGH' — Maximum severity found among findings. - `skillName` string — Name of the skill that produced this analysis. - `findings` Finding[] — Findings produced by the analysis. - `location` FindingLocation — Location details with file path and line number. - `filePath` string — Relative path of the file containing the finding. - `lineNumber` string, int64 — Line number (1-based), or 0 if whole File / unknown. - `severity` 'SEVERITY_UNSPECIFIED' | 'CRITICAL' | 'HIGH' — Severity of the finding. - `scanner` 'SCANNER_UNSPECIFIED' | 'STATIC' | 'LLM' | 'WS_POLICY' | 'GOOGLE_ANTIVIRUS' — Scanner determines which engine (e.g. static, llm) emitted the finding. - `category` string — Category of the finding. - `details` string — Description of the finding category. - `name` string — Output only. The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`. - `secret` SecretOccurrence — The occurrence provides details of a secret. - `locations` SecretLocation[] — Optional. Locations where the secret is detected. - `fileLocation` GrafeasV1FileLocation — Indicates the location at which a package was found. - `layerDetails` LayerDetails — Details about the layer a package was found in. - `chainId` string — The layer chain ID (sha256 hash) of the layer in the container image. https://github.com/opencontainers/image-spec/blob/main/config.md#layer-chainid - `diffId` string — The diff ID (typically a sha256 hash) of the layer in the container image. - `index` integer — The index of the layer in the container image. - `command` string — The layer build command that was used to build the layer. This may not be found in all layers depending on how the container image is built. - `baseImages` BaseImage[] — The base images the layer is found within. - … - `filePath` string — For jars that are contained inside .war files, this filepath can indicate the path to war file combined with the path to jar file. - `lineNumber` integer — Line number in the file where the package was found. Optional field that only applies to source repository scanning. - `statuses` SecretStatus[] — Optional. Status of the secret. - `status` 'STATUS_UNSPECIFIED' | 'UNKNOWN' | 'VALID' | 'INVALID' — Optional. The status of the secret. - `updateTime` string, google-datetime — Optional. The time the secret status was last updated. - `message` string — Optional. Optional message about the status code. - `kind` 'SECRET_KIND_UNSPECIFIED' | 'SECRET_KIND_UNKNOWN' | 'SECRET_KIND_GCP_SERVICE_ACCOUNT_KEY' | 'SECRET_KIND_GCP_API_KEY' | 'SECRET_KIND_GCP_OAUTH2_CLIENT_CREDENTIALS' | 'SECRET_KIND_GCP_OAUTH2_ACCESS_TOKEN' | 'SECRET_KIND_ANTHROPIC_ADMIN_API_KEY' | 'SECRET_KIND_ANTHROPIC_API_KEY' | 'SECRET_KIND_AZURE_ACCESS_TOKEN' | 'SECRET_KIND_AZURE_IDENTITY_TOKEN' | 'SECRET_KIND_DOCKER_HUB_PERSONAL_ACCESS_TOKEN' | 'SECRET_KIND_GITHUB_APP_REFRESH_TOKEN' | 'SECRET_KIND_GITHUB_APP_SERVER_TO_SERVER_TOKEN' | 'SECRET_KIND_GITHUB_APP_USER_TO_SERVER_TOKEN' | 'SECRET_KIND_GITHUB_CLASSIC_PERSONAL_ACCESS_TOKEN' | 'SECRET_KIND_GITHUB_FINE_GRAINED_PERSONAL_ACCESS_TOKEN' | 'SECRET_KIND_GITHUB_OAUTH_TOKEN' | 'SECRET_KIND_HUGGINGFACE_API_KEY' | 'SECRET_KIND_OPENAI_API_KEY' | 'SECRET_KIND_PERPLEXITY_API_KEY' | 'SECRET_KIND_STRIPE_SECRET_KEY' | 'SECRET_KIND_STRIPE_RESTRICTED_KEY' | 'SECRET_KIND_STRIPE_WEBHOOK_SECRET' — Required. Type of secret. - `noteName` string — Required. Immutable. The analysis note associated with this occurrence, in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`. This field can be used as a filter in list requests. - `remediation` string — A description of actions that can be taken to remedy the note. - `kind` 'NOTE_KIND_UNSPECIFIED' | 'VULNERABILITY' | 'BUILD' | 'IMAGE' | 'PACKAGE' | 'DEPLOYMENT' | 'DISCOVERY' | 'ATTESTATION' | 'UPGRADE' | 'COMPLIANCE' | 'DSSE_ATTESTATION' | 'VULNERABILITY_ASSESSMENT' | 'SBOM_REFERENCE' | 'SECRET' | 'AI_SKILL_ANALYSIS' — Output only. This explicitly denotes which of the occurrence details are specified. This field can be used as a filter in list requests. - `package` PackageOccurrence — Details on how a particular software package was installed on a system. - `cpeUri` string — Output only. The cpe_uri in [CPE format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package. The cpe_uri will be blank for language packages. - `name` string — Required. Output only. The name of the installed package. - `location` Location[] — All of the places within the filesystem versions of this package have been found. - `path` string — The path from which we gathered that this package/version is installed. - `cpeUri` string — Deprecated. The CPE URI in [CPE format](https://cpe.mitre.org/specification/) - `version` Version — Version contains structured information about the version of a package. - `kind` 'VERSION_KIND_UNSPECIFIED' | 'NORMAL' | 'MINIMUM' | 'MAXIMUM' — Required. Distinguishes between sentinel MIN/MAX versions and normal versions. - `revision` string — The iteration of the package build from the above version. - `epoch` integer — Used to correct mistakes in the version numbering scheme. - `fullName` string — Human readable version string. This string is of the form :- and is only set when kind is NORMAL. - `name` string — Required only when version kind is NORMAL. The main part of the version name. - `inclusive` boolean — Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range. - `license` License — License information. - `expression` string — Often a single license can be used to represent the licensing terms. Sometimes it is necessary to include a choice of one or more licenses or some combination of license identifiers. Examples: "LGPL-2.1-only OR MIT", "LGPL-2.1-only AND MIT", "GPL-2.0-or-later WITH Bison-exception-2.2". - `comments` string — Comments - `version` Version — Version contains structured information about the version of a package. - `kind` 'VERSION_KIND_UNSPECIFIED' | 'NORMAL' | 'MINIMUM' | 'MAXIMUM' — Required. Distinguishes between sentinel MIN/MAX versions and normal versions. - `revision` string — The iteration of the package build from the above version. - `epoch` integer — Used to correct mistakes in the version numbering scheme. - `fullName` string — Human readable version string. This string is of the form :- and is only set when kind is NORMAL. - `name` string — Required only when version kind is NORMAL. The main part of the version name. - `inclusive` boolean — Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range. - `packageType` string — Output only. The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.). - `architecture` 'ARCHITECTURE_UNSPECIFIED' | 'X86' | 'X64' — Output only. The CPU architecture for which packages in this distribution channel were built. Architecture will be blank for language packages. - `attestation` AttestationOccurrence — Occurrence that represents a single "attestation". The authenticity of an attestation can be verified using the attached signature. If the verifier trusts the public key of the signer, then verifying the signature is sufficient to establish trust. In this circumstance, the authority to which this attestation is attached is primarily useful for lookup (how to find this attestation if you already know the authority and artifact to be verified) and intent (for which authority this attestation was intended to sign. - `jwts` Jwt[] — One or more JWTs encoding a self-contained attestation. Each JWT encodes the payload that it verifies within the JWT itself. Verifier implementation SHOULD ignore the `serialized_payload` field when verifying these JWTs. If only JWTs are present on this AttestationOccurrence, then the `serialized_payload` SHOULD be left empty. Each JWT SHOULD encode a claim specific to the `resource_uri` of this Occurrence, but this is not validated by Grafeas metadata API implementations. The JWT itself is opaque to Grafeas. - `compactJwt` string — The compact encoding of a JWS, which is always three base64 encoded strings joined by periods. For details, see: https://tools.ietf.org/html/rfc7515.html#section-3.1 - `serializedPayload` string, byte — Required. The serialized payload that is verified by one or more `signatures`. - `signatures` Signature[] — One or more signatures over `serialized_payload`. Verifier implementations should consider this attestation message verified if at least one `signature` verifies `serialized_payload`. See `Signature` in common.proto for more details on signature structure and verification. - `signature` string, byte — The content of the signature, an opaque bytestring. The payload that this signature verifies MUST be unambiguously provided with the Signature during verification. A wrapper message might provide the payload explicitly. Alternatively, a message might have a canonical serialization that can always be unambiguously computed to derive the payload. - `publicKeyId` string — The identifier for the public key that verifies this signature. * The `public_key_id` is required. * The `public_key_id` SHOULD be an RFC3986 conformant URI. * When possible, the `public_key_id` SHOULD be an immutable reference, such as a cryptographic digest. Examples of valid `public_key_id`s: OpenPGP V4 public key fingerprint: * "openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA" See https://www.iana.org/assignments/uri-schemes/prov/openpgp4fpr for more details on this scheme. RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization): * "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU" * "nih:///sha-256;703f68f42aba2c6de30f488a5ea122fef76324679c9bf89791ba95a1271589a5" - `envelope` Envelope — MUST match https://github.com/secure-systems-lab/dsse/blob/master/envelope.proto. An authenticated message of arbitrary type. - `signatures` EnvelopeSignature[] - `sig` string, byte - `keyid` string - `payloadType` string - `payload` string, byte ## Response `200` Successful response --- [API](https://skmtc.dev/google/apis/containeranalysis.md) · [All operations](https://skmtc.dev/google/apis/containeranalysis/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/containeranalysis/revisions/024ed008c491/schema)