Issue card information

Introduction to issue cards

Issue cards appear on the details page for a Project.
You can:

View Issue card information

Issue cards show details for a specific vulnerability or license issue, and actions you can take for:
Issue card for the npmconf vulnerability
Issue card for the npmconf vulnerability
Card details include Header section and Body section information.

Header section

npmconf issue card header
npmconf issue card header
  • Severity level: for example, H (High) or C (Critical)
  • Issue name: for example, Uninitialized Memory Exposure, with a link that can be copied
  • Score: Priority score: 0 - 1,000
  • Links to CWE (Common Weakness Evaluation), CVSS (Common Vulnerability Scoring System), and Snyk Intel Vulnerability DB information for the issue. You can use these links to view more information about the CWE, CVE, and CVSS scores: or navigate to the Snyk vulnerability database information for a specific vulnerability from its issue card.

Body section

npmconf issue card body details
npmconf issue card body details
  • Introduced through: The path through which the vulnerability or license was introduced
  • Fixed in: The file the vulnerability is fixed in
  • Exploit maturity: for example, Mature or Proof Of Concept
  • Reachability: for example, Reachable. For information and an example, see Reachable vulnerabilities
  • Social Trends: Snyk shows a Trending banner for issues that are being actively discussed on Twitter.

Detailed information in the issue card

When you expand the issue card for more information, you can see details for the vulnerability, including:
  • Detailed path information
  • Fix advice
  • Overview of the vulnerability
  • Any vulnerable functions within the vulnerability
Details for the npmconf vulnerability
Details for the npmconf vulnerability

Filtering and sorting issue cards

You can apply multiple filters to a Project to show a set of issues:
  • Whether a vulnerability or a license issue
  • With a specific severity
  • Within a range of the priority score
  • Based on whether it has an exploit, and how mature the exploit is
  • That are open or have been patched or ignored
The issue cards in a Project can be sorted based on their priority score or severity.

Card actions

You can perform the following actions on the issue card:
  • Ignore the issue: if you do not need to take action on an issue, or it does not need to appear on your reports, you can ignore it.
  • ****Create a Jira ticket: if you have the Jira integration, you can link your issue boards to Snyk and create Jira tickets directly from the project details page to fix vulnerabilities.
  • Fix the vulnerability: if a fix is available, you can fix individual vulnerabilities.