Skip to main content
Version: 2608.1

summary.json


Description

A file containing summary information about the analysis. It includes the analysis result, the number of vulnerabilities, analysis time information, and so on.

File

{
"analysisId" : "ANALYSIS_ID",
"requestId" : "REQUEST_ID",
"status" : "COMPLETE",
"result" : "SUCCESS",
"toolType" : "TYPE",
"startTime" : "YYYY-MM-DDThh:mm:ss.sss±hh:mm",
"endTime" : "YYYY-MM-DDThh:mm:ss.sss±hh:mm",
"issueCount" : "TOTAL_ISSUES",
"issueCountRisk1" : "TRIVIAL_ISSUES",
"issueCountRisk2" : "LOW_ISSUES",
"issueCountRisk3" : "MEDIUM_ISSUES",
"issueCountRisk4" : "HIGH_ISSUES",
"issueCountRisk5" : "CRITICAL_ISSUES"
"memo" : "MEMO",
"versions" : "W: WORKER_VERSION, S: SAST_VERION, C: SCA_VERSION, D: DAST_VERSION",
"checkersHash" : "CHECKER_HASH",
"resultVersion" : "2",
"type" : "VCS",
"url" : "VCS_URL",
"branch" : "BRANCH_NAME",
"commitId" : "COMMIT_ID",
"tag": "TAG_NAME",
"bucket" : "BUCKET",
"object" : "OBJECT_NAME",
"endpoint" : "ENDPOINT",
"cloneSize" : "CLONE_SIZE",
"fileCount" : "RAW_FILES",
"componentCount" : "COMPONENTS",
"targetCount" : "TARGET_FILES",
"codeSize": "CODE_SIZE",
"targetUrl": "URL",
"urlCount": "URLS",
"requestCount": "REQUESTS",
"workerId" : "WORK_ID",
"resultCode" : "ERROR_CODE",
"failStatus" : null
}
  • analysisId Analysis ID
    An ID generated uniquely for the analysis. You can use it later to look up information about the analysis. For details, see Analysis inquiry.
  • requestId Request ID
    An ID generated uniquely for the request. You can use it later to look up information about the request. For details, see Request inquiry.
  • status Analysis status
    The status according to the phase the analysis is in. It is shown as one of the following.
    • STOP_PROCESS: stopping the analysis after receiving a stop request
    • INIT : preparing the environment to run the analysis
    • READY: the environment is configured and the analysis target is being prepared
    • PRE_PROCESS: pre-processing the analysis target for the analysis
    • ANALYSIS: the analysis is running
    • POST_PROCESS: the analysis has finished and the results are being processed
    • COMPLETE: the analysis has ended
  • result Analysis result
    The result with which the analysis ended. It takes one of the following values.
    • SUCCESS: the analysis completed successfully
    • FAIL: the analysis did not complete correctly and failed
    • STOP: the analysis was stopped after a stop request
  • toolType Analysis type
    The type of the requested analysis (TYPE). It takes one of the following values.
    • SAST: source code analysis
    • SCA: open source analysis
    • DAST: web vulnerability analysis
  • startTime Analysis start timestamp
    Shows the date and time the analysis started in the following format.(YYYY-MM-DDThh:mm:ss.sss±hh:mm)
  • endTime Analysis end timestamp
    Shows the date and time the analysis ended in the following format.(YYYY-MM-DDThh:mm:ss.sss±hh:mm)
  • issueCount Total number of issues
    The number of issues detected in the analysis (TOTAL_ISSUES).
  • issueCountRisk1 Number of issues with risk level Very low
    The number of detected issues is classified into five risk levels: Very high, High, Medium, Low, and Very low. This is the number of issues classified as Very low (TRIVIAL_ISSUES).
  • issueCountRisk2 Number of issues with risk level Low
    The number of detected issues is classified into five risk levels: Very high, High, Medium, Low, and Very low. This is the number of issues classified as Low (LOW_ISSUES).
  • issueCountRisk3 Number of issues with risk level Medium
    The number of detected issues is classified into five risk levels: Very high, High, Medium, Low, and Very low. This is the number of issues classified as Medium (MEDIUM_ISSUES).
  • issueCountRisk4 Number of issues with risk level High
    The number of detected issues is classified into five risk levels: Very high, High, Medium, Low, and Very low. This is the number of issues classified as High (HIGH_ISSUES).
  • issueCountRisk5 Number of issues with risk level Very high
    The number of detected issues is classified into five risk levels: Very high, High, Medium, Low, and Very low. This is the number of issues classified as Very high (CRITICAL_ISSUES).
  • memo Memo
    The description entered when the analysis was requested.
  • versions Versions
    The versions of the Sparrow On-Demand worker and engines used for the analysis(W: WORKER_VERSION, S: SAST_VERION, C: SCA_VERSION, D: DAST_VERSION).
  • checkersHash Analysis rule file hash
    The hash of the Sparrow On-Demand analysis rule file used for the analysis(CHECKER_HASH). It is shown so that you can tell whether the same rules were used for an analysis.
  • resultVersion Result version
    The version of the analysis results.
  • type Analysis target type
    The analysis target type entered when the analysis was requested. It is shown only when toolType is SAST or SCA.
    • VCS: analyzes the source in a VCS repository.
    • OBJECT_STORAGE: analyzes the source in object storage.
  • url VCS URL
    The URL (VCS_URL) of the repository where the files to be analyzed are stored. It is shown when type is VCS.
  • branch Branch
    The name of the branch (BRANCH_NAME) to which the files you want to analyze were uploaded. It is shown when type is VCS.
  • commitId Commit ID
    The commit ID (COMMIT_ID) you want to analyze. It is shown when type is VCS.
  • tag Tag
    The tag information (TAG_NAME) of the branch you want to analyze. It is shown when type is VCS.
  • bucket Storage bucket
    It is shown when type is OBJECT_STORAGE.
  • endPoint Storage endpoint
    It is shown when type is OBJECT_STORAGE.
  • object Storage object name
    It is shown when type is OBJECT_STORAGE.
  • cloneSize Size of the cloned analysis target
    The size of the analysis target cloned from the original analysis target(CLONE_SIZE). It is shown only when toolType is SAST or SCA.
  • fileCount Number of original files
    The number of files included in the original analysis target(RAW_FILES). It is shown only when toolType is SAST or SCA.
  • componentCount Number of components in the analysis target
    The number of components detected in the analysis(COMPONENTS). It is shown only when toolType is SAST or SCA.
  • targetCount Number of analyzed files
    The number of analysis targets, among the original analysis targets, that were used to extract components(TARGET_FILES). It is shown only when toolType is SAST or SCA.
  • codeSize Size of the analyzed source code
    The size of the source code, among the original analysis targets, that was used in the analysis(CODE_SIZE). It is shown only when toolType is SAST or SCA.
  • targetUrl Analysis target URL
    The analysis target URL entered when the analysis was requested(URL). It is shown only when toolType is DAST.
  • urlCount Number of crawled URLs
    The number of URLs crawled from the analysis target URL during the analysis(URLS). It is shown only when toolType is DAST.
  • requestCount Number of requests
    The number of attack requests sent to the analysis target URL during the analysis(REQUESTS). It is shown only when toolType is DAST.
  • workerId Worker ID
    The unique ID of the worker in the environment configured for the analysis(WORK_ID).
  • resultCode Result code
    The result code shown when the analysis did not end normally(ERROR_CODE). For details about the codes shown, see Analysis result codes.
  • failStatus Analysis status at the time of failure
    If the analysis did not end normally and failed, the analysis status is shown as one of the following.
    • STOP_PROCESS: the analysis is being stopped after receiving a stop request.
    • INIT : waiting for resource allocation to run the analysis.
    • READY: the phase in which resources have been allocated and the analysis target is being prepared. Example) downloading the source code
    • PRE_PROCESS: the phase in which various pre-processing tasks are performed before the analysis starts. Example) collecting analysis targets
    • ANALYSIS: the analysis is running.
    • POST_PROCESS: the phase in which the analysis has finished and the results are being processed.