Snyk Code prioritizes vulnerabilities using a Priority Score, which is an integer number between 1 and 1000 that indicates the severity of the vulnerability and its potential impact on the application's security. The score takes into account various factors such as the severity assigned by the scanning engine, occurrences of the vulnerability, hotfiles, previous fixes, and commonly fixed vulnerabilities in open-source repositories. The Priority Score is recalculated every time a snapshot and scan are performed, and it can be sorted by Priority Score for speedy prioritization. To optimize the use of the Priority Score, engineers should filter the result set to an upper and lower threshold of the Priority Score, always use the latest score value, avoid comparing scores from different Snyk solutions, and hover over the score to understand the reasons behind it.