Dependency Analytics is powered by Snyk Intel Vulnerability DB. It is the most advanced and accurate open source vulnerability database in the industry and adds value with the latest, fastest, and numerous vulnerabilities derived from multiple sources.
'Dependency Analytics Report' with Insights about your application dependencies:
- Flags a security vulnerability(CVE) and suggests a remedial version
- Shows Github popularity metrics along with the latest version
- Suggests a project level license, check for conflicts between dependency licenses
- AI-based guidance for additional, alternative dependencies
Disclaimer: Dependency Analytics does not analyse dev/test dependencies.
'Dependency Analytics' extension supports projects using Maven, npm (Node ecosystem), Python, and Golang. Extending support for other languages is currently in progress.
This extension assumes you have the following binaries on your PATH
:
mvn
(for analyzing Java applications)npm
(for analyzing Node applications)python
(for analyzing Python applications)go
(for analyzing Golang applications)
Note: By default, the mvn/npm/go
command is executed directly in the terminal, which requires that mvn/npm/go
is found in your system environment PATH
. For Python applications Interpreter Path is required to be provided as below.
You can do this via preferences in VS Code:
File(Code on macOS) > Preferences > Settings to open your Settings select Workspace (open settings.json) and add below.
{
...
"maven.executable.path": "/path-to-maven-home/bin/mvn"
"npm.executable.path": "/path-to-npm-home/bin/npm"
"python.pythonPath": "/path-to-python-home/bin/python"
"go.executable.path": "/path-to-go/bin/go"
...
}
NOTE Dependency Analytics is an online service hosted and maintained by Red Hat. This open source software will access only your manifests and license file(s) to learn about application dependencies and licenses before giving you the report.
- Install the extension.
- Opening or editing a manifest file (
pom.xml
/package.json
/requirements.txt
/go.mod
) scans your application for security vulnerabilities. - Right click on a manifest file (
pom.xml
/package.json
/requirements.txt
/go.mod
) in the 'Vscode File explorer' or 'Vscode File editor' to display 'Dependency Analytics Report' for your application.
- Opening or editing a manifest file (
pom.xml
/package.json
/requirements.txt
/go.mod
) scans your application for security vulnerabilities, flag them along with 'Quick Fix'.
- 'Quick Fix' provides a single-click option to
Switch to the recommended version
for vulnerability remediation. It also provides an option forDetailed Vulnerability Report
to display 'Dependency Analytics' report with detailed vulnerability analysis.
- Right-click on a manifest file(
pom.xml
/package.json
/requirements.txt
) and choose 'Dependency Analytics Report ...' OR click on icon in editor group OR click on status bar message to display 'Dependency Analytics' report as shown below. This report covers deeper insights into your application dependencies:
- Flags a security vulnerability(CVE) and suggests a remedial version
- Shows Github popularity metrics along with the latest version
- Suggests a project level license, check for conflicts between dependency licenses
- AI-based guidance for additional, alternative dependencies
- For multi-module maven application Right-click on root
pom.xml
in the editor window and choose Dependency Analytics Report ...' so display 'Dependency Analytics' report for the entire application.
Note It creates a folder target
in the workspace, used to process manifest files needed for generating stack reports. Please add target
in .gitignore
.
- Clicking on the
Sign up for a free Snyk account
from 'Dependency Analytics report' will take you to the Snyk sign-up page for a free Snyk account. After signing up for a free Snyk account, it goes to the 'Snyk's Landing page', which showsSnyk token
to connect Snyk with your Red Hat Dependency Analytics. Copy and paste the Snyk token into Red Hat Dependency Analytics Report below.
- Look for in Dependency Analytics Report and click on the button to enter your Snyk Token. Paste your Snyk token and click on the
Submit button
.
- After successfully entering the Snyk token, the Dependency Analytics report updates with detailed information about security vulnerabilities unique to Snyk and vulnerabilities having publicly known exploits.
If users wish to ignore vulnerabilities for a dependency, it can be done by adding "crdaignore" as a comment in the manifest file for Python, Maven, Golang. Node manifest files don't support comments; hence "crdaignore" must be given inside a JSON. If "crdaignore" is followed by a list of comma-separated Snyk vulnerability IDs, only listed vulnerabilities ignored during analysis, in case "crdaignore" is not followed by any list, all vulnerabilities present in a package will be ignored.
Ignore all vulnerabilities in fastapi and few for flask
fastapi==0.36.0 #crdaignore
sceptre==2.2.1
flask==1.0 #crdaignore [<Snyk vulnerability ID 1 >, <Snyk vulnerability ID 2 >]
Ignore all the security vulnerabilities present in the "ginkgo" and "pax-go" dependencies in a golang manifest file.
code.cloudfoundry.org/archiver v0.0.0-20170223024658-7291196139d7
github.com/googleapis/gax-go v1.0.3 //crdaignore [<Snyk vulnerability ID 1 >]
github.com/googleapis/gax-go/v2 v2.0.5
github.com/onsi/ginkgo v1.14.2 // indirect crdaignore
github.com/onsi/gomega v1.10.3 // indirect
Ignore all vulnerabilities of the dependency "junit:junit".
<dependency>
<groupId>junit</groupId> <!--crdaignore-->
<artifactId>junit</artifactId>
<version>3.8.1</version>
</dependency>
Note: To ignore vulnerabilities for a dependency in a maven manifest file, insert "crdaignore" in comments against the group id, artifact id, or version of that particular dependency.
Ignore all the security vulnerabilities for "bootstrap" and a set of vulnerabilities for the "lodash" package.
"crdaignore": {
"packages": {
"bootstrap": [
"*"
],
"lodash": [<Snyk vulnerability ID 1 >]
}
},
A sample npm manifest file with the security vulnerabilities to ignore during analysis:
{
"name": "node-js-sample",
"version": "0.2.0",
"description": "A sample Node.js app using Express 4",
"main": "index.js",
"scripts": {
"start": "node index.js"
},
"dependencies": {
"ansi-styles": "3.2.1",
"escape-string-regexp": "1.0.5",
"supports-color": "5.5.0",
"cordova-plugin-camera": "4.1.0",
"bootstrap": "4.1.1",
"libnmap": "0.4.15",
"lodash": "4.17.11",
"html-purify": "1.1.0"
},
"engines": {
"node": "4.0.0"
},
"crdaignore": {
"packages": {
"bootstrap": [
"*"
],
"lodash": ["vulnerability 1"]
}
},
"repository": {
"type": "git",
"url": "https://github.com/heroku/node-js-sample"
},
"keywords": [
"node",
"heroku",
"express"
],
"author": "Mark Pundsack",
"contributors": [
"Zeke Sikelianos <zeke@sikelianos.com> (http://zeke.sikelianos.com)"
],
"license": "MIT"
}
You can use the CodeReady Dependency Analytics GitHub Action to automate analysis of vulnerabilities in a project's dependencies. Refer to action's documentation or this article on how to set it up for your projects.
The mission of this project is to enhance developer experience significantly: providing Insights(security, licenses, AI based guidance) for applications and helping developers, Enterprises.
-
VScode output says "Go executable not found".
Suggestion: Try adding your go executable path to your vscode's settings.json file
E.g.:
"go.executable.path": "/path-to-go/bin/go"
-
Failed to run golist command.
Suggestion: Resolve the error thrown by
go mod tidy
andgo list
for the project and try again. -
Stack analysis fails after applying the recommended version.
Suggestion: Not all recommended versions work directly, developers need to resolve dependencies for the recommended version using
go mod tidy
or manually. -
Plugin does not highlight vulnerabilities in vendor code.
Suggestion: Currently plugin does not support vendor (or local) code vulnerabilities scanning. Switch to go.mod to express your project dependencies.
- File a bug in GitHub Issues
Apache 2.0, See LICENSE for more information.
The Red Hat Dependency Analytics Extension for Visual Studio Code collects anonymous usage data and sends it to Red Hat servers to help improve our products and services. Read our privacy statement to learn more. This extension respects the redhat.elemetry.enabled
setting which you can learn more about at https://github.com/redhat-developer/vscode-commons#how-to-disable-telemetry-reporting