Skip to main content

IDE and Pipeline scans explore data dictionary

These definitions describe the dimensions and measures used on the IDE and Pipeline Scans explore in Veracode Analytics.

IDE and Pipeline scans dimensions

Account NameThe account name provided in the Veracode Platform.
IDEThe development environment in which the scan ran.
IDE VersionThe version of the IDE where the scan started. If empty, it was an API scan.
OSThe operating system of the IDE that the user is using.
Plugin VersionThe version of the Veracode IDE scan plugin or Pipeline Scan JAR file.
Project NameOptional field for the name of the project containing the scanned files, where applicable.
Project ReferenceOptional field for the source control reference, revision, or branch of the development project.
Project URIOptional field for the URI of the development project.
Results Size (MB)The size of the JSON results file (MB).
Scan End DateThe date and time the scan completed. Possible values are date, month, month name, quarter, time, week, and year.
Scan LanguageThe language of the files to be scanned.
Scan Start DateThe date and time the scan started. Possible values are date, month, month name, quarter, time, week, and year.
Scan StatusThe status of the scan.
Scan TypeHow the scan was submitted. Active = User-Initiated IDE Scan, Passive = Auto-Initiated IDE Scan, API = Pipeline Scan API, DevOps = Pipeline Scan Pre-Release, Pipeline = Pipeline Scan.
User EmailThe email address of the user who submitted the scan.
User TimeoutUser-defined value for the number of seconds to wait before a scan times out. This field only populates if you provide a value.

IDE and Pipeline scans measures

Scan CountsThe total count of unique scans.
User CountsThe count of distinct users.