# get-code-finding ## Description Retrieves the current state and details of a finding. See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/continuum-2022-07-26/GetCodeFinding) ## Synopsis ``` get-code-finding --environment-id --finding-id [--cli-input-json | --cli-input-yaml] [--generate-cli-skeleton ] [--debug] [--endpoint-url ] [--no-verify-ssl] [--no-paginate] [--output ] [--query ] [--profile ] [--region ] [--version ] [--color ] [--no-sign-request] [--ca-bundle ] [--cli-read-timeout ] [--cli-connect-timeout ] [--cli-binary-format ] [--no-cli-pager] [--cli-auto-prompt] [--no-cli-auto-prompt] [--cli-error-format ] ``` ## Options `--environment-id` (string) [required] > The environment that owns the finding. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` `--finding-id` (string) [required] > The unique identifier of the finding to retrieve. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` `--cli-input-json` | `--cli-input-yaml` (string) Reads arguments from the JSON string provided. The JSON string follows the format provided by `--generate-cli-skeleton`. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with `--cli-input-yaml`. `--generate-cli-skeleton` (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value `input`, prints a sample input JSON that can be used as an argument for `--cli-input-json`. Similarly, if provided `yaml-input` it will print a sample input YAML that can be used with `--cli-input-yaml`. If provided with the value `output`, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated. ## Global Options `--debug` (boolean) Turn on debug logging. `--endpoint-url` (string) Override command’s default URL with the given URL. `--no-verify-ssl` (boolean) By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates. `--no-paginate` (boolean) Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results. `--output` (string) The formatting style for command output. * json * text * table * yaml * yaml-stream * off `--query` (string) A JMESPath query to use in filtering the response data. `--profile` (string) Use a specific profile from your credential file. `--region` (string) The region to use. Overrides config/env settings. `--version` (string) Display the version of this tool. `--color` (string) Turn on/off color output. * on * off * auto `--no-sign-request` (boolean) Do not sign requests. Credentials will not be loaded if this argument is provided. `--ca-bundle` (string) The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings. `--cli-read-timeout` (int) The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds. `--cli-connect-timeout` (int) The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds. `--cli-binary-format` (string) The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob `fileb://` will always be treated as binary and use the file contents directly regardless of the `cli-binary-format` setting. When using `file://` the file contents will need to properly formatted for the configured `cli-binary-format`. * base64 * raw-in-base64-out `--no-cli-pager` (boolean) Disable cli pager for output. `--cli-auto-prompt` (boolean) Automatically prompt for CLI input parameters. `--no-cli-auto-prompt` (boolean) Disable automatically prompt for CLI input parameters. `--cli-error-format` (string) The formatting style for error output. By default, errors are displayed in enhanced format. * legacy * json * yaml * text * table * enhanced ## Output type -> (string) > What kind of finding this is. Determines which of the type-specific members below are populated. > Possible values: > * `CONTINUUM_CODE_VULN` > * `CUSTOMER_CODE_VULN` title -> (string) > The producer’s title for the finding. > Constraints: > * min: `1` > * max: `2048` severity -> (string) > The finding’s severity. > Possible values: > * `UNKNOWN` > * `INFORMATIONAL` > * `LOW` > * `MEDIUM` > * `HIGH` > * `CRITICAL` > * `FATAL` > * `OTHER` summary -> (string) > A one-paragraph description. > Constraints: > * min: `1` > * max: `65536` detailedDescription -> (string) > The full analysis. > Constraints: > * min: `1` > * max: `65536` category -> (string) > The producer’s vulnerability category. Not a stable filter key across finding types – see FindingCategory. > Constraints: > * min: `1` > * max: `512` subCategory -> (string) > A more specific classification within `category` . > Constraints: > * min: `1` > * max: `512` cweIds -> (list) > CWE identifiers classifying the finding. > Constraints: > * min: `0` > * max: `64` > (string) > > A CWE identifier, e.g. “CWE-532”. > > Constraints: > > * min: `1` > > * max: `64` owaspCategory -> (string) > The OWASP Top 10 category, when the producer supplies one. > Constraints: > * min: `1` > * max: `512` mitigation -> (string) > How to fix the finding. > Constraints: > * min: `1` > * max: `65536` filePath -> (string) > The file the finding is about. > Constraints: > * min: `1` > * max: `4096` lineNumber -> (integer) > The 1-indexed line the finding is about. Bounds are enforced server-side rather than by a constraint trait: a numeric constraint generates a distinct newtype per enclosing structure, so the same concept would not share a type across the create input and the read output. cveId -> (string) > The CVE this finding reports, for software-composition findings. Both code types can carry one: a customer document supplies it under vulnerabilities[].cve, and Continuum’s scanner reports CVEs for dependency-manifest findings. > Constraints: > * min: `1` > * max: `64` cvssBaseScore -> (double) > The CVSS base score accompanying `cveId` , when the producer supplies one, from 0.0 to 10.0. Not computed by Continuum. The range is enforced server-side, not by a @range trait – the smithy-rs server SDK does not support range constraints on double shapes (smithy-rs#2007). affectedPackages -> (list) > Packages implicated by the finding. > Constraints: > * min: `0` > * max: `256` > (structure) > > A software package implicated by a finding. > > name -> (string) [required] > > > The package name. > > > Constraints: > > > * min: `1` > > > * max: `512` > > version -> (string) > > > The affected version. > > > Constraints: > > > * min: `1` > > > * max: `256` > > fixedInVersion -> (string) > > > The earliest version that resolves the issue, when one is known. > > > Constraints: > > > * min: `1` > > > * max: `256` > > packageManager -> (string) > > > The ecosystem supplying the package. > > > Constraints: > > > * min: `1` > > > * max: `128` vulnerableCode -> (string) > The vulnerable code fragment. > Constraints: > * min: `1` > * max: `32768` relevantInputs -> (list) > User-controlled inputs that reach the vulnerability. > Constraints: > * min: `0` > * max: `256` > (string) > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > Constraints: > > * min: `1` > > * max: `8192` stepsToReproduce -> (list) > Steps to reproduce or exploit the finding. > Constraints: > * min: `0` > * max: `256` > (string) > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > Constraints: > > * min: `1` > > * max: `8192` validation -> (structure) > The validator’s assessment. Absent when no validation ran. > verdict -> (string) [required] > > The validator’s conclusion. > > Possible values: > > * `TRUE_POSITIVE` > > * `FALSE_POSITIVE` > > * `BENIGN_TRUE_POSITIVE` > > * `NEEDS_REVIEW` > blockingReason -> (string) > > Why the validator reached that verdict. > > Possible values: > > * `UNREACHABLE` > > * `PROTECTED` > > * `MISCLASSIFIED` > > * `EXCLUDED` > > * `NOT_FEASIBLE` > > * `RISK_MITIGATED` > > * `NONE` > confidence -> (double) > > The validator’s confidence, from 0.0 to 1.0 inclusive. Advisory: it does not drive Continuum’s own routing decisions. The range is enforced server-side, not by a @range trait – the smithy-rs server SDK does not support range constraints on double shapes (smithy-rs#2007). > rationale -> (string) > > The validator’s reasoning. > > Constraints: > > * min: `1` > > * max: `65536` > severityAdjustment -> (string) > > The validator’s severity conclusion. > > Possible values: > > * `CRITICAL` > > * `HIGH` > > * `MEDIUM` > > * `LOW` > > * `INFORMATIONAL` > > * `UNCHANGED` > mitigatingControls -> (list) > > Controls the validator found that reduce exploitability. > > Constraints: > > * min: `0` > > * max: `256` > > (string) > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > Constraints: > > > * min: `1` > > > * max: `8192` > preconditions -> (list) > > Conditions exploitation depends on, which bound the severity. > > Constraints: > > * min: `0` > > * max: `256` > > (string) > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > Constraints: > > > * min: `1` > > > * max: `8192` > evidence -> (list) > > Code citations supporting the verdict. > > Constraints: > > * min: `0` > > * max: `64` > > (structure) > > > A code citation supporting a validation verdict. > > > file -> (string) > > > > The file the evidence was found in. > > > > Constraints: > > > > * min: `1` > > > > * max: `4096` > > > line -> (integer) > > > > The 1-indexed line, when known. > > > snippet -> (string) > > > > The cited excerpt. > > > > Constraints: > > > > * min: `1` > > > > * max: `32768` endLine -> (integer) > The last line of the affected range, from the document’s affected_code[].end_line. mitreTechniques -> (list) > MITRE ATT&CK technique identifiers, from the document’s finding_info.attacks[].technique.uid. > Constraints: > * min: `0` > * max: `256` > (string) > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > Constraints: > > * min: `1` > > * max: `8192` remediationReferences -> (list) > Remediation references, from the document’s vulnerabilities[].remediation.references. > Constraints: > * min: `0` > * max: `256` > (string) > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > Constraints: > > * min: `1` > > * max: `8192` ocsfClass -> (string) > The OCSF class the document declared. Determines whether `posture` is populated. > Possible values: > * `VULNERABILITY_FINDING` > * `APPLICATION_SECURITY_POSTURE_FINDING` ocsfSchemaVersion -> (string) > The OCSF schema version the producer wrote against (metadata.version). > Constraints: > * min: `1` > * max: `512` productName -> (string) > The producing product and vendor (metadata.product). > Constraints: > * min: `1` > * max: `512` productVendorName -> (string) > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > Constraints: > * min: `1` > * max: `512` productVersion -> (string) > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > Constraints: > * min: `1` > * max: `512` sourceStatus -> (string) > The producer’s own status for the finding, and the enum value behind it. Distinct from `status` , which is Continuum’s lifecycle state – a producer may call a finding “New” while Continuum has it SUBMITTED. > Constraints: > * min: `1` > * max: `512` sourceStatusId -> (integer) > The producer’s numeric enum value for `sourceStatus` . firstSeenAt -> (timestamp) > When the producer first observed the finding (finding_info.first_seen_time). The producer’s own clock, not Continuum’s. findingTypes -> (list) > The producer’s own classification of the finding (finding_info.types). > Constraints: > * min: `0` > * max: `256` > (string) > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > Constraints: > > * min: `1` > > * max: `8192` vulnerabilities -> (list) > Every vulnerability the document reported. A document may report several; the flat `cveId` /`cvssBaseScore` /`filePath` /`lineNumber` members above carry the first one’s identity so a caller that only needs “what and where” does not have to walk this list. > Constraints: > * min: `0` > * max: `256` > (structure) > > One vulnerability reported by a finding. A customer document may report several; each carries its own identity, locations and remediation. > > title -> (string) > > > The title of a finding, from the producer’s own title – OCSF finding_info.title, or the scanner’s finding title. Length matches the OCSF title constraint. > > > Constraints: > > > * min: `1` > > > * max: `2048` > > description -> (string) > > > Free-form prose about a finding (summary, detailed analysis, rationale, remediation guidance). Capped well below the finding document’s own 256 KB limit, since several of these can appear on one finding. > > > Constraints: > > > * min: `1` > > > * max: `65536` > > cweId -> (string) > > > Primary CWE for this vulnerability, e.g. “CWE-89”. > > > Constraints: > > > * min: `1` > > > * max: `64` > > cweCaption -> (string) > > > The producer’s human-readable caption for `cweId` . > > > Constraints: > > > * min: `1` > > > * max: `512` > > additionalCweIds -> (list) > > > Further CWEs the producer attributed to this same vulnerability. > > > Constraints: > > > * min: `0` > > > * max: `64` > > > (string) > > > > A CWE identifier, e.g. “CWE-532”. > > > > Constraints: > > > > * min: `1` > > > > * max: `64` > > cveId -> (string) > > > A CVE identifier, e.g. “CVE-2020-8203”. > > > Constraints: > > > * min: `1` > > > * max: `64` > > cvssBaseScore -> (double) > > > The CVSS base score for `cveId` , when the producer supplies one, from 0.0 to 10.0. > > fixCoverage -> (string) > > > The producer’s description of how completely a fix is available. > > > Constraints: > > > * min: `1` > > > * max: `512` > > fixCoverageId -> (integer) > > > The producer’s enum value behind `fixCoverage` . > > locations -> (list) > > > Every location this vulnerability was reported at. > > > Constraints: > > > * min: `0` > > > * max: `64` > > > (structure) > > > > A code location a finding points at. > > > > filePath -> (string) > > > > > Repository-relative path. > > > > > Constraints: > > > > > * min: `1` > > > > > * max: `4096` > > > > startLine -> (integer) > > > > > 1-indexed first line of the affected range. > > > > endLine -> (integer) > > > > > 1-indexed last line, when the producer reported a range. > > remediation -> (string) > > > Free-form prose about a finding (summary, detailed analysis, rationale, remediation guidance). Capped well below the finding document’s own 256 KB limit, since several of these can appear on one finding. > > > Constraints: > > > * min: `1` > > > * max: `65536` > > remediationReferences -> (list) > > > A free-form list of strings carried verbatim from a producer. > > > Constraints: > > > * min: `0` > > > * max: `256` > > > (string) > > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > > Constraints: > > > > * min: `1` > > > > * max: `8192` > > code -> (string) > > > The vulnerable fragment, when the producer supplied one. > > > Constraints: > > > * min: `1` > > > * max: `32768` > > details -> (string) > > > The producer’s extended analysis for this vulnerability. > > > Constraints: > > > * min: `1` > > > * max: `65536` > > affectedPackages -> (list) > > > Software packages implicated by a finding. > > > Constraints: > > > * min: `0` > > > * max: `256` > > > (structure) > > > > A software package implicated by a finding. > > > > name -> (string) [required] > > > > > The package name. > > > > > Constraints: > > > > > * min: `1` > > > > > * max: `512` > > > > version -> (string) > > > > > The affected version. > > > > > Constraints: > > > > > * min: `1` > > > > > * max: `256` > > > > fixedInVersion -> (string) > > > > > The earliest version that resolves the issue, when one is known. > > > > > Constraints: > > > > > * min: `1` > > > > > * max: `256` > > > > packageManager -> (string) > > > > > The ecosystem supplying the package. > > > > > Constraints: > > > > > * min: `1` > > > > > * max: `128` resources -> (list) > Resources the document named (resources[]). > Constraints: > * min: `0` > * max: `256` > (structure) > > A cloud or application resource a finding concerns. > > uid -> (string) > > > A resource identifier – a cloud ARN, a context-graph node id, or whatever identifier scheme the producer uses. > > > Constraints: > > > * min: `1` > > > * max: `2048` > > name -> (string) > > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > > Constraints: > > > * min: `1` > > > * max: `512` > > type -> (string) > > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > > Constraints: > > > * min: `1` > > > * max: `512` > > region -> (string) > > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > > Constraints: > > > * min: `1` > > > * max: `512` posture -> (structure) > The compliance posture, for an Application Security Posture Finding. Absent for a vulnerability finding. > application -> (string) > > The application the posture was assessed against. > > Constraints: > > * min: `1` > > * max: `512` > applicationUid -> (string) > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > Constraints: > > * min: `1` > > * max: `512` > applicationVersion -> (string) > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > Constraints: > > * min: `1` > > * max: `512` > control -> (string) > > The control assessed, and the producer’s description of it. > > Constraints: > > * min: `1` > > * max: `512` > description -> (string) > > Free-form prose about a finding (summary, detailed analysis, rationale, remediation guidance). Capped well below the finding document’s own 256 KB limit, since several of these can appear on one finding. > > Constraints: > > * min: `1` > > * max: `65536` > standards -> (list) > > Standards and requirements the control maps to. > > Constraints: > > * min: `0` > > * max: `256` > > (string) > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > Constraints: > > > * min: `1` > > > * max: `8192` > requirements -> (list) > > A free-form list of strings carried verbatim from a producer. > > Constraints: > > * min: `0` > > * max: `256` > > (string) > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > Constraints: > > > * min: `1` > > > * max: `8192` > checks -> (list) > > The individual checks performed. > > Constraints: > > * min: `0` > > * max: `256` > > (structure) > > > One compliance check behind a posture finding. > > > uid -> (string) > > > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > > > Constraints: > > > > * min: `1` > > > > * max: `512` > > > name -> (string) > > > > A vulnerability-taxonomy label: the producer’s category, sub-category, or OWASP category. Deliberately unconstrained beyond length – producers do not share a taxonomy, so this is NOT a stable filter key across finding types. Use `cweIds` when a stable classification is needed. > > > > Constraints: > > > > * min: `1` > > > > * max: `512` > > > description -> (string) > > > > Free-form prose about a finding (summary, detailed analysis, rationale, remediation guidance). Capped well below the finding document’s own 256 KB limit, since several of these can appear on one finding. > > > > Constraints: > > > > * min: `1` > > > > * max: `65536` > status -> (string) > > The producer’s compliance status, and the enum value behind it. > > Constraints: > > * min: `1` > > * max: `512` > statusId -> (integer) > > The producer’s numeric enum value for `status` . > remediation -> (string) > > Free-form prose about a finding (summary, detailed analysis, rationale, remediation guidance). Capped well below the finding document’s own 256 KB limit, since several of these can appear on one finding. > > Constraints: > > * min: `1` > > * max: `65536` > remediationReferences -> (list) > > A free-form list of strings carried verbatim from a producer. > > Constraints: > > * min: `0` > > * max: `256` > > (string) > > > One entry in a free-form list carried verbatim from a producer (relevant inputs, reproduction steps, mitigating controls, preconditions, references). > > > Constraints: > > > * min: `1` > > > * max: `8192` findingId -> (string) > The unique identifier of the finding. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` findingArn -> (string) > The ARN of the finding. > Constraints: > * min: `1` > * max: `1011` > * pattern: `arn:[a-z0-9-]+:continuum:[a-z0-9-]+:[0-9]{12}:environments/[a-z0-9]+/code-findings/[a-z0-9]+` environmentId -> (string) > The environment that owns the finding. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` source -> (string) > The system that produced the finding. > Constraints: > * min: `1` > * max: `256` sourceFindingId -> (string) > The producer’s own identifier for the finding. > Constraints: > * min: `1` > * max: `1024` reportedAt -> (timestamp) > When the producer reported the finding – its own clock, which is not Continuum’s ingestion time. `createdAt` is when Continuum accepted it; these are genuinely different instants and a reader usually wants this one. > For CreateCodeFinding, this is the submitted OCSF document’s own top-level `time` . For findings Continuum’s scanner produces, it is the finding’s own creation time. > Continuum does not validate it for plausibility: a producer’s value is echoed as given, so a `timestamp` here asserts the unit and format, not that the instant is genuine. status -> (string) > The current lifecycle status of the finding. > Possible values: > * `SUBMITTED` > * `VALIDATING` > * `CONFIRMED` > * `DISCARDED` statusUpdatedAt -> (timestamp) > The timestamp when the status last transitioned. createdAt -> (timestamp) > The timestamp when the finding was ingested. scanRunId -> (string) > The scan that produced the finding, when it came from one. For a finding Continuum’s scanner produced, this is the Continuum scan run (see GetCodeScan). For a finding submitted with CreateCodeFinding, it is the OCSF document’s `metadata.correlation_uid` , when that value is a valid ScanRunId. Absent when the finding did not come from a scan. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` statusMessage -> (string) > Human-readable context about the current status. > Constraints: > * min: `1` > * max: `1024` discardReason -> (string) > Why the finding was not escalated. Present only when status is DISCARDED. > Possible values: > * `SCANNER_VALIDATED_FALSE_POSITIVE` > * `SCANNER_NEEDS_REVIEW` > * `FALSE_POSITIVE_VALIDATED_AGAINST_CONTEXT` > * `DUPLICATE_OF_OPEN_ISSUE` > * `DUPLICATE_OF_CLOSED_ISSUE` > * `COMPENSATING_CONTROL_PRESENT` > * `OUT_OF_SCOPE` > * `INSUFFICIENT_EVIDENCE` > * `PROCESSING_FAILED` > * `SOURCE_REPO_NOT_FOUND` discardReasoning -> (string) > Customer-facing explanation accompanying `discardReason` . > Constraints: > * min: `1` > * max: `1024` duplicateOfIssueId -> (string) > The existing issue this finding duplicates. Present only for the DUPLICATE_OF_\* discard reasons. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` createdIssueId -> (string) > The issue Continuum created from this finding. > Constraints: > * min: `1` > * max: `64` > * pattern: `[a-z0-9]+` completedAt -> (timestamp) > When processing finished, whether by creating an issue or discarding. Absent while the finding is still in flight.