pysnyk

A Python client for the Snyk API.

Client

Using the client requires you to provide your Snyk API token.

import snyk
client = snyk.SnykClient("<your-api-token>")

By default the client will connect to the public Snyk service. If you are using a local installation then you can provide the API url as the second argument.

import snyk
client = snyk.SnykClient("<your-api-token>", "<your-instance-of-snyk>")

By default the User-Agent string for the API requests will be pysnyk/<version>. If you would like to send a custom user agent you can do so as follows:

import snyk
client = snyk.SnykClient("<your-api-token>", user_agent="<your-instance-of-snyk>")

Organizations

With the client we can get a list of Snyk organizations you are a member of:

client.organizations.all()

This returns a list of snyk.models.Organization objects.

If you already have the ID of the organization you're after you can grab it directly:

client.organizations.get("<organization-id>")

This will return a single snyk.models.Organization object.

Most of the API is scoped to organizations, so most other methods are found on the snyk.models.Organization objects returned by these two methods.

The snyk.models.Organization object has the following properties related to the API:

• entitlements - returns the set of Snyk features available to this account
• dependencies- returns a Manager for packages in use in this organization
• licenses - returns a Manager for licenses currently in use by projects in this organisation
• members - returns a Manager for members
• projects - returns a Manager for associated projects
• integrations - returns a Manager for active integrations

A note on Managers

Managers provide a consistent API for accessing objects from the Snyk API. Each manager implements the following methods:

• all() - return a list of all of the relevant objects
• get("<id>") - return a single instance of the object if it exists
• first() - grab the first instance of the object if one exists
• filter(<key>="<value>") - return a list filtered by one or more key/value pairs

Projects

Once you have an organization you're likely to want to grab the related projects:

client.organizations.first().projects.all()

This will return a list of snyk.models.Project objects.

In the case where you want to get all of the projects across all of your organizations then you can use the handy method on the client.

client.projects.all()

The snyk.models.Project object has the following useful properties and methods:

• delete() - deletes the project in question. We careful as this will delete all associated data too
• dependencies - returns a Manager for packages in use in this project
• dependency_graph - returns a snyk.models.DependencyGraph object which represents the full dependency graph of package dependencies
• ignores - returns a Manager for ignore rules set on the project
• vulnerabilies - returns a list of snyk.models.Vulnerability objects with information about vulnerabilities in this project
• jira_issues - returns a Manager with access to any associated Jira issues
• licenses - returns a Manager for licenses currently in use by this project
• settings - returns a Manager for interacting with the current project settings

Note that the settings Manager can also be used to update settings like so, assumibg you have a snyk.models.Project object in the variable project.

project.settings.update(pull_request_test_enabled=True)

Importing new projects

The client supports a high-level import_project method on organizations for adding new projects to be monitored by Snyk.

org = client.organizations.first()
org.import_project("github.com/user/project@branch")
org.import_project("docker.io/repository:tag")

This method currently only supports importing projects from GitHub and Docker Hub. For other integrations you will need to grab the lower-level snyk.models.Integration object from the snyk.models.Organization.integrations manager noted above. Other services will be added to this API soon.

Testing for vulnerabilties

The API also exposes meythods to discover vulnerability information about individual packages. These methods are found on the Organization object.

• test_maven(<package_group_id>, <package_artifact_id>, <version>) - returns an IssueSet containing vulnerability information for a Maven artifact
• test_rubygem(<name>, <version>) - returns an IssueSet containing vulnerability information for a Ruby Gem
• test_python(<name>, <version>) - returns an IssueSet containing vulnerability information for Python package from PyPi
• test_npm(<name>, <version>) - returns an IssueSet containing vulnerability information for an NPM package

Here's an example of checking a particular Python package.

>>> org = client.organizations.first()
>>> result = org.test_python("flask", "0.12.2")
>>> assert result.ok
False
# You can access details of the vulnerabilities too, for example
>>> result.issues.vulnerabilities[0].title
'Improper Input Validation'
>>> result.issues.vulnerabilities[0].identifiers
{'CVE': ['CVE-2018-1000656'], 'CWE': ['CWE-20']

As well as testing individual packages you can also test all packages found in various dependency management manifests. The client currently supports the following methods:

• test_pipfile(<file-handle-or-string>) - returns an IssueSet for all Python dependencies in a Pipfile
• test_gemfilelock(<file-handle-or-string>) - returns an IssueSet for all Ruby dependencies in a Gemfile
• test_packagejson(<file-handle-or-string>) - returns an IssueSet for all Javascript dependencies in a package.json file
• test_gradlefile(<file-handle-or-string>) - returns an IssueSet for all dependencies in a Gradlefile
• test_sbt(<file-handle-or-string>) - returns an IssueSet for all dependencies defined in a .sbt file
• test_pom(<file-handle-or-string>) - returns an IssueSet for all dependencies in a Maven pom.xml file

For example, here we are testing a Python Pipfile.

>>> org = client.organizations.first()
>>> file = open("Pipfile")
>>> org.test_pipfile(file)

Low-level client

As well as the high-level API of the Snyk client you can use the HTTP methods directly. For these you simply need to pass the path, and optionally a data payload. The full domain, and the authentication details, are already provided by the client.

client.get("<path>")
client.delete("<path>")
client.put("<path>", <data>)
client.post("<path>", <data>)

Most of the time you shouldn't need to use these. They are mainly useful if new methods are added to the API which are not yet supported in the client. This can also be useful if you want to pass very specific parameters, or to parse the raw JSON output from the API.