Getting started
Quickstart
One command installs the scanner and signs your machine in. A second one runs your first scan. The same scan runs in CI with a Workspace Token.
Install and sign in
The installer prints a link and opens it in your browser. Sign in with GitHub if you have not yet (your personal workspace is created for you), check that the page shows the same code as your terminal, and approve. The installer then downloads the build for your machine, verifies its checksum, and stores the sign-in on this machine.
macOS, Linux, WSL:
curl -fsSL https://atmoslab.dev/install.sh | bash
Windows PowerShell:
irm https://atmoslab.dev/install.ps1 | iex
Windows CMD:
curl -fsSL https://atmoslab.dev/install.cmd -o install.cmd && install.cmd && del install.cmd
The scanner installs to ~/.local/bin (%LOCALAPPDATA%\Atmos\bin on Windows). To pin a version, pass it as an argument: bash -s 1.2.3, or install.cmd 1.2.3. Over SSH, or when no browser opens, copy the printed link into any browser.
To confirm the install worked, run:
atmos --version
From here on, atmos self-update keeps the binary current, and atmos logout signs the machine out. Every machine you sign in on is listed on the dashboard's Tokens page, where you can revoke it.
Run your first scan
cd your-project atmos scan .
atmos scan checks your code and your dependencies in one run and closes with one summary. Findings appear in your terminal and, seconds later, on your dashboard. The project onboards itself on the first scan. To run one check alone, use atmos sast . or atmos sca .
Add Atmos to CI
CI and other headless environments use a Workspace Token instead of a sign-in. Create one on the dashboard's Tokens page (owners and admins), store it as a secret, and use it both to download the scanner and to scan:
curl -fL -H "Authorization: Bearer $ATMOS_TOKEN" \ "https://ingest.atmoslab.dev/v1/cli/download?artifact=linux-x86_64" \ -o atmos && chmod +x atmos
- run: atmos scan . env: ATMOS_TOKEN: ${{ secrets.ATMOS_TOKEN }}
Use curl 7.58 or newer. The exit code decides the build. With the GitHub App connected, findings also show on the pull request. See pull request feedback.