Using Snyk with Travis

Snyk + TCI

Snyk is a developer security platform. Integrating directly into development tools, which means it can integrate with Travis. In this example, I’ll show you how Snyk is going to scan multiple filetypes like a Dockerfile that has Palantir’s Apache Cassandra instance, or a simple Terraform config file, and other components in my Travis configuration, so let’s take a quick look before we deploy our newest idea to the world.


Let’s define the language in the .travis.yml as node. You’ll notice we are also grabbing pipenv, because in the repository I’ll be giving you at the end of this, I will have an example for Python as well. Let’s take a look at my .travis.yml config:

  - pip install pipenv
language: node_js
  - lts/*
  - npm install -g snyk@latest # Globally install Snyk via node package manager, using condition `@latest` for latest version.
  - snyk -v # Print out the current version of Snyk symlinked. 
  - snyk code
  - snyk test --docker debian --file=Dockerfile --exclude-base-image-vulns # Scan the Palantir Cassandra container. 
  - snyk iac test # Test an IaC method, say in this case Terraform. With simple variables that really equal to moot.

Snyk Environment Variables

It’s important to note you’ll need your Snyk env vars. You’ll need to fetch those from Snyk, and then name the env var something like SNYK_TOKEN.

Things that we will be testing

So, in this particular use case of Travis and Snyk, I decided to grab Palantir’s Dockerfile of Apache Cassandra, the Dockerfile is as follows:

FROM cassandra:2.2



# Untar the Palantir distribution

ADD palantir-cassandra-*tgz /

# We give the cassandra user permissions to create things in the Cassandra dir

RUN ["sh", "-c", "chmod +rwx ${CASSANDRA_DIR}"]
RUN ["sh", "-c", "chown cassandra:cassandra ${CASSANDRA_DIR}"]

# Configs set up for Travis/Snyk scans via yaml, and some bash scripting

COPY cassandra.yaml $CASSANDRA_YAML

ENV _JAVA_OPTIONS=-Dcassandra.skip_wait_for_gossip_to_settle=0

# Enable wide JMX access for tests, copied from

RUN sed -i s/'jmxremote.authenticate=true'/'jmxremote.authenticate=false'/g $CASSANDRA_ENV

# Entry set up

RUN ["chmod", "+x", "/"]

EXPOSE 7000 7001 7199 9042 9160
CMD ["cassandra", "-f"]`

Okay, so you have your Dockerfile the .travis.yml file I made, time to get Snyk up and running, open up your CLI and run the following in your project directory:

snyk auth


Follow the prompts, and now maybe do a trial run in your CLI, run the following command:

snyk test --docker debian --file=Dockerfile --exclude-base-image-vulns

In this case I used the --exclude-base-image-vulns flag when it’s running the checks on the Palantir Cassandra Dockerfile, this is something similar you’ll see when you run it locally:


Testing IaC’s With Snyk and Travis CI

Now let’s say you have a Terraform config file, named the classic, and want to check that, pretty simple to do that as well. So let’s make a test Terraform config file in HCL, here’s what I coded out for this example:

provider "local" {
  version = "~> 1.4"
resource "local_file" "hello snyk, montana, palantir, cassandra and travis" {
  content = "Hello, user"
  filename = "foobar.txt"

Now that we have saved in the directory, just run the following in your CLI while you’re doing the local tests:

snyk iac test

You should see something that resembles the following:


Travis CI

Alright, well now that you have a basic understand of what Snyk does and how we are going to integrate it into our Travis project, let’s first trigger a build, you’ll want to remember those env vars, when it starts building, you’ll see that Snyk gets pulled via npm install -g snyk@latest, then I have it run snyk -v which tells you what version of Snyk you’re running inside of Travis, then it will start going on ahead with the testing:


You’ll start seeing Snyk doing these to any of the files you declared in your .travis.yml, making sure there are close to no vulnerabilities. You can also test containers, so for example you can run in your CLI:

snyk container monitor <your-image>

You can also add this to your .travis.yml, so let’s say I had a container over at Docker entitled container.tar, we could add this line in our script: hook in our Travis config file:

- snyk container test docker-archive:container.tar


Well there you have it, making things secure is always important when it comes to software development, end to end and up and down the stack. You now know how to integrate Snyk with your Travis CI builds, just another presentation of how flexible Travis CI is using integrations.

Here is my example of the Travis and Snyk integration, click here.

As always remember if you have any questions, any questions at all, please email me at

Happy building!