Travis CI
Travis CICI/CD3 credentials
API Token
travis-ci / api-token
Travis CI API tokens authenticate CLI and API clients for repository, build, and environment-variable management.
Location
Travis-API-VersionUsed alongside Authorization in Travis API requests
Authorizationtoken used by Travis CI API clients
Travis CLI config, .travis.yml encrypted variables workflow, scripts, and .env files
TRAVIS_TOKEN, TRAVIS_API_TOKENpassword managers, CI variables, and deployment vaults
automation repos and accidentally committed configs
CLI debug output and curl traces
Repository Environment Variable / Encrypted Variable
travis-ci / env-var-secret
Travis CI repository settings and .travis.yml encrypted variables hold deployment credentials, cloud keys, package tokens, and passwords injected into builds.
Location
Travis repository environment variables and encrypted variables
.travis.ymlencrypted env/global values and deploy provider settings
runtime build environment variables injected by Travis CI
repository CI configuration and deployment scripts
build logs if secrets are printed or masking fails
Deploy Key / Provider Token
travis-ci / deploy-key-and-provider-secret
Travis deployment providers and repository access features use SSH keys, GitHub tokens, package tokens, and cloud credentials to publish artifacts.
Looks like
pattern-----BEGIN (RSA |OPENSSH |EC |)PRIVATE KEY-----Location
.travis.ymldeploy provider token fields and encrypted credentials
Travis secure env vars and deployment provider secrets
deployment scripts and release tooling
deployment logs and provider CLI debug output
Scope
Authorized use
LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.