Travis CI

Collect repository, build, and environment-variable-config evidence as read-only CI/CD compliance signal through the Travis CI API.

Connect Travis CI All integrations

CI · CD

Tier 2 generic template — runs on the HTTP / REST endpoint connector

Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

Read-only API inventory endpoint checks
Evidence assets generated through the generic HTTP connector

Read-only calls

Endpoints this template queries

The exact Travis CI API endpoints called once connected. All read-only GET requests unless noted.

GET/repos
GET/builds?limit=50
GET/user

Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

Base URL(prefilled: https://api.travis-ci.com)
Endpoints (JSON)(prefilled: [ { "id": "repos", "name": "Repositories", "path": "/repos" }, { "id": "builds", "name": "Builds", "path": "/builds?limit=50" }, { "id": "user", "name": "User", "path": "/user" } ])

Optional

Auth header name(prefilled: Authorization)
Auth header value(secret credential)

Where this evidence goes

Which frameworks this evidence supports

Travis CI evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Travis CI evidence

Get a guided demo, or start by scanning any domain for free.

Connect Travis CI Browse all integrations