CLI
command not found: octopoda
The installer put octopoda in a folder that is not on your PATH. It prints the folder and the line to add when this happens, for example:
~/.zshrc or ~/.bashrc) and open a new terminal.
you are not signed in. Run: octopoda login
Run octopoda login. In CI, set the OCTOPODA_TOKEN environment variable instead. See Run Octopoda scans in CI.
The browser does not open when you sign in
Over SSH, or with--no-browser, the CLI prints the link instead of opening it. Open the link on any device where you can sign in, check that the code matches, and approve.
the code expired. Run octopoda login again
The sign-in code was not approved in time. Run octopoda login again and approve it in the browser.
this project is larger than 200 MB without dependencies
Leave out generated files, build output or large fixtures with a .octopodaignore file. See Choose what gets scanned.
no finding F-142 in this account
The finding belongs to another account, or the key is wrong. Run octopoda whoami to see which account the CLI is signed in to, and check the key on the Findings page.
Windows
The CLI runs on macOS and Linux. On Windows, install and run it inside WSL.Scans
The scan does not start because of credits
A code scan needs 5 credits and a pull request scan needs 1. Buy a top-up on the Billing page or wait for your plan to renew. See Plans and credits.Scans are paused
A payment failed. Update your card on the Billing page; scans resume once the payment succeeds. See Manage billing.The scan stays queued
Your plan runs a limited number of scans at the same time (1 on Builder, 2 on Pro, 5 on Team). A queued scan starts when one of your running scans finishes. Cancel scans you no longer need from their scan page.The scan ended as partial
It reached its time or budget limit before testing everything. Its findings are proven. For a large project, give the next scan focus with--instructions, for example the part of the app you changed.
The scan failed
Open the scan page to see why. If it failed on our side, its credits were refunded and you can run it again. If it keeps failing, email support with the scan link.GitHub
A pull request was not scanned
Check these in order:- The pull request is a draft. Drafts are scanned once they are marked ready for review.
- Checks are off for the repository. Turn on Scan every pull request on the Repositories page.
- The check says Not scanned. The account is out of credits, has no plan or has a failed payment. Fix it on the Billing page, then push again.
- The repository shows Access removed on GitHub. Select Restore access to give the GitHub App access again.