Pinpoint CLI

A single native binary with zero runtime dependencies. Drop it into any CI/CD pipeline or run it locally from the terminal.

v1.2.2LINUXMACOSWINDOWSDOCKER

01/INSTALL

ONE BINARY. ANY PLATFORM.

Choose your platform, copy the commands, and you are ready to go. Each tab includes architecture-specific instructions.

ARCHITECTURE

Most cloud servers, CI runners, and desktops

Download the binary

curl -fSL -o pinpoint https://testwithpinpoint.com/downloads/cli/latest/pinpoint-linux-amd64

Make it executable
```
chmod +x pinpoint
```

Move to your PATH

sudo mv pinpoint /usr/local/bin/pinpoint

Verify the installation
```
pinpoint --version
```

FOUR COMMANDS TO A WORKING BINARY

02/CONFIGURE

ONE TOKEN. EVERY SHELL.

Run the built-in configure command to validate and persist your credentials. For CI/CD environments, environment variables remain the preferred method.

Run the configure command
This validates your token, discovers your account, and saves credentials to ~/.pinpoint/config.json
```
pinpoint configure --token "your-api-token"
```
Verify the configuration
If configured correctly, this will show your projects
```
pinpoint projects list
```

ENV VARS ARE THE CI DEFAULT

03/USAGE

RUN THE ROUND FROM THE PROMPT.

Once installed and configured, use these commands to manage projects, trigger test rounds, download reports, and resolve bugs from the terminal.

NEED THE BINARY FIRST? INSTALL FOR LINUX, MACOS, OR WINDOWS →

TerminalBASH

Create a project

pinpoint projects create --name "My App" --type UI

Create a test request

Start a new QA test round for a specific project

pinpoint requests create --project "abc-1234-def"

Check request status

View the current state of a test request

pinpoint requests get abc-1234-def

Download a report PDF

Get the presigned URL for a report and download it locally

pinpoint reports download abc-1234-def | xargs curl -o report.pdf

List open bugs

View all open bug reports for your project

pinpoint bugs list --status open

Mark bug as complete

Mark a bug as fixed with a resolution note (Pinpoint verifies before closing)

pinpoint bugs update abc-1234-def --status complete \
  --resolution "Fixed null check in refund handler"

Trigger a test round

Start a new QA round against your staging environment

pinpoint trigger \
  --project "my-app" \
  --build-url "https://ci.example.com/builds/4821"

THE CLI YOUR PIPELINE ALREADY RUNS

04/Spectre

Spectre SHIPS INSIDE.

Run static analysis locally or in CI to surface architectural issues, security vulnerabilities, and blast radius. Review and manage findings directly from the terminal. All Spectre commands ship inside the Pinpoint CLI, so the entrypoint is always pinpoint spectre scan, not a separate spectre binary.

NOT INSTALLED YET? BACK TO INSTALL →

TerminalBASH

Run a Spectre scan on your codebase

Scan for architectural issues, security vulnerabilities, and blast radius from the repository root

pinpoint spectre scan . \
  --project "abc-1234-def"

Scan a specific subdirectory

Narrow the scan scope to a single service or module within a monorepo

pinpoint spectre scan . \
  --project "abc-1234-def" --scope code/api

Restrict to specific languages

Limit analysis to chosen language stacks for faster scans on large repos

pinpoint spectre scan . \
  --project "abc-1234-def" --languages java,typescript

Fail CI on high-severity findings

Use as a quality gate in your pipeline to block deploys when critical issues surface

pinpoint spectre scan . \
  --project "abc-1234-def" --fail-on high

List Spectre findings

Review results filtered by severity, category, or status

pinpoint spectre findings list --project "abc-1234-def" \
  --severity HIGH --status OPEN

View finding details

Inspect a single finding with full context, blast radius score, and remediation guidance

pinpoint spectre findings show abc-1234-def

Resolve a finding

Update a finding status to acknowledged, resolved, or false positive

pinpoint spectre findings update abc-1234-def \
  --project "abc-1234-def" --status RESOLVED

Check scan quota usage

View how much of your monthly Spectre scan budget has been consumed

pinpoint spectre findings usage --project "abc-1234-def"

SAME BINARY · SAME TOKEN · SAME PIPELINE

DOWNLOAD IT. WIRE IT IN.

The same binary runs in your pipeline, your terminal, and your containers. For the full picture of how the CLI fits a Pinpoint engagement, see how it works end to end.

THE CLI IN YOUR PIPELINE →

Apply for Access

ONE BINARY ◦ ZERO RUNTIME DEPENDENCIES ◦ ANY CI RUNNER