Data Share Data Dictionary
Snyk Data Share is a comprehensive dataset encompassing various data pillars that support a wide range of use cases. You can use this dataset to present key security metrics such as issue backlog, aging, MTTR, SLA compliance, and test coverage, as well as to prioritize issues based on different factors, such as risk score, severity, CVSS, EPSS, and many more.
This dictionary is designed to help you navigate the dataset efficiently, with clear explanations of each table's purpose and the specific data contained in each column, enabling you to leverage the X dataset to meet your data reporting needs.
Data Share Tables
The diagram above represents the objects listed in the data dictionary as a database diagram. It covers the following tables:
Groups
current version: v1.0
The GROUPS
table contains the main attributes of Snyk Groups. This data can be utilized for performing aggregations on the Group level or for zooming into the scope of specific Groups.
Column name | Data type | Description |
---|---|---|
| varchar | A universally unique identifier for a Group, assigned i the records source database. |
| varchar | The name of this group. |
| varchar | The name of the Group within Snyk. |
| timestamp_ntz | When this record was created in Snyk. |
| timestamp_ntz | When this record was deleted from Snyk. |
| timestamp_ntz | When this record was last modified within Snyk. |
| timestamp_ntz | When the data share data transformation last updated this record. |
Orgs
current version: v1.0
The ORGS
table contains the main attributes of Snyk Organizations. This data can be utilized for performing aggregations on the organization level or for zooming into the scope of specific organizations.
The group_public_id
column allows you to query organizations in specific groups.
Column name | Data type | Description |
---|---|---|
| varchar | A universally unique identifier for an organization, assigned in the records source database. |
| varchar | A universally unique identifier for a group, assigned in the records source database. |
| varchar | The display name set for this organization. |
| varchar | The name for the Organization within Snyk. |
| timestamp_ntz | When this record was created in Snyk. |
| timestamp_ntz | When this record was deleted from Snyk. |
| timestamp_ntz | When this record was last modified within Snyk. |
| timestamp_ntz | When the data share data transformation last updated this record. |
Projects
current version: v1.0
The PROJECTS
table contains main attributes of Snyk Projects, as well as the related target. Its data can be utilized for performing aggregations of filters on the project or target levels, including based on project collections, project tags or specific repo branches (using target_ref
).
Snyk Reports only presents monitored projects that were not deleted. To match your results with Snyk Reports, filter your query with IS_MONITORED = TRUE
and DELETE IS NULL.
Column name | Data type | Description |
---|---|---|
| varchar | A universally unique identifier for a project, assigned in the record's source database. |
| varchar | A universally unique identifier for an organisation, assigned in the record's source database. |
| varchar | A universally unique identifier for a group, assigned in the record's source database. |
| varchar | The name given to this project, when added to Snyk. |
| boolean | Whether this project is currently set to be actively monitored. |
| varchar | The scanning method to use for a particular Project, such as Static Application Security Testing (SAST) for scanning using Snyk Code, or Maven for a Maven project using Snyk Open Source. This is part of the configuration for scanning. |
| varchar | A display name Snyk assigned to internal project type values. |
| varchar | The frequency of testing for a given Project. For example, Daily, Weekly, and so on. |
| varchar | The Origin defines the Target ecosystem, such as CLI, GitHub, or Kubernetes. Origins are a property of Targets. |
| varchar | A reference that differentiates this project, for example, a branch name or version. Projects having the same reference can be grouped based on that reference. |
| varchar | The environment in which the Target is executed and run. |
| varchar | A display name for a project's target. |
| boolean | Whether the target's source is private or publicly reachable. |
| varchar | The hosting provider of a given target, for example, docker-hub, github, and so on. |
| varchar | A display value that represents the grouping for target sources, for example, Source Control, Container Registry, and so on. |
| varchar | The URL pointing to a target's upstream source, such as a URL for a GitHub repository. |
| array | A project attribute that indicates business criticality. For example, low, medium, high, critical. |
| array | A project attribute, for example, production, development, sandbox. |
| array | A project attribute, for example, frontend, backend, internal, external, mobile, saas, onprem, hosted, distributed. |
| array | All Project collections to which this project has been added. |
| array | All tags which have been assigned to this project. |
| varchar | The email of the user assigned as the owner of this project. |
| varchar | The username of the user assigned as the owner of this project. |
| timestamp_ntz | When this record was created in Snyk. |
| timestamp_ntz | When this record was deleted from Snyk. |
| timestamp_ntz | When this record was last modified within Snyk. |
| timestamp_ntz | When the data share data transformation last updated this record. |
Issues
current version: v1.0
The ISSUES
table contains various attributes of Snyk Issues. Issues can be easily correlated with their originating project, target, org or group, utilizing the corresponding ID columns. On top of the issue's basic attributes, such as its introduction date, type, severity, score, etc., there are columns that elaborate on the vulnerability attributes, such as the CVSS score, EPSS Score, NVD Score, etc.
Querying the issues table allows:
Concluding various metrics and KPIs, among issue backlog, aging, MTTR and SLA compliance.
Visualizing trends of identified, ignored, resolved issues over time
Prioritize issues based on multiple factors and considerations
If you would like to match your results with Snyk Reports, filter your query with DELETE IS NULL
, as Snyk Reports don't present deleted issues.
computed_fixability
indicates whether the issue can be fixed based on the vulnerability remediation paths, for example:
Fixable: There is a fix for all the identified issues, meaning that all detailed paths have remediation.
Partially fixable: The issue has upgradable paths, but not all detailed paths have remediation.
No supported fix: The issue has no upgradable paths.
Column name | Data type | Description |
---|---|---|
| varchar | A unique identifier, representing a unique instance of a given vulnerability in a project. |
| varchar | Snyk Vulnerability database ID that uniquely identifies the vulnerability. |
| varchar | A universally unique identifier for a project, assigned in the record's source database. |
| varchar | A universally unique identifier for an organization, assigned in the record's source database. |
| varchar | A universally unique identifier for a group, assigned in the record's source database. |
| varchar | The Snyk Product which initially identified this issue. |
| varchar | Name of the Snyk discovered vulnerability. |
| varchar | URL which directs to the Snyk's Public Vulnerability Database website. |
| varchar | Indicates whether the issue is related to a vulnerability, license, or configuration. |
| varchar | A more granular variation of issue type. |
| varchar | URL which directs to the given's project's instance of this vulnerability on the Snyk Website. |
| varchar | Indicates whether the issue is open, resolved, or ignored. |
|