Install CS Code where your source code already lives.
The CLI scans locally, generates release evidence locally and only talks to the dashboard when you explicitly upload metadata with a scoped token.
Authentication model
local firstLocal scan
No account, token or network connection required.
Pack/evidence/diff
Runs locally and writes files into the release-pack folder.
Dry-run upload
No API call. It prints exactly what would be uploaded.
Metadata upload
Requires a scoped CLI token created in the dashboard.
Evidence PDF upload
Optional and explicit. Standard upload is metadata-summary only.
Downloads
A real CS Code CLI artifact, plus auditable package options.
Private beta artifacts are served directly from this deployment. Verify downloads with SHA-256 before use. macOS and Windows native binaries should be built on those platforms before broader public distribution.
Linux binary
One-file executable for Linux/WSL
DownloadPython wheel
Install with pip on Python 3.12+
DownloadSource package
Auditable Python source package
DownloadChecksums
SHA-256 hashes for download verification
DownloadLinux / WSL binary
downloadcurl -fsSL https://cs-code.com/downloads/cli/cscode-linux-x86_64 -o cscode
chmod +x cscode
./cscode doctorOne-file private-beta binary built from this repository. Install Syft and Grype locally for real SBOM/vulnerability results.
Python package
downloadpython3 -m venv .venv
source .venv/bin/activate
pip install https://cs-code.com/downloads/cli/cscode_cli-0.1.0-py3-none-any.whl
cscode doctorCross-platform private-beta package for Linux, macOS and WSL when Python 3.12+ is available.
Install helper
downloadcurl -fsSL https://cs-code.com/downloads/cli/install-linux.sh | bash
cscode doctorInstalls the Linux binary into ~/.local/bin. Use this for a fast private-beta trial on Linux/WSL.
Docker CLI
repo-localdocker compose --profile tools run --rm cli doctor
docker compose --profile tools run --rm cli pack examples/demo-compose-app-v2 --product "Demo App" --version "2.0.0"Useful when Docker is already installed and you want an isolated CLI runtime from this repository.
Common commands
From local pack to optional dashboard metadata.
No account required
cscode pack ./my-app --product "My Product" --version "1.2.3" --exclude ".env" --exclude "secrets/**"Generate buyer pack
cscode evidence release-pack-my-product-1.2.3
cscode export release-pack-my-product-1.2.3 --format pdfPreview upload
cscode upload --dry-run release-pack-my-product-1.2.3Dashboard upload
cscode auth login --api-url https://app.cs-code.com --token <CLI_TOKEN>
cscode upload release-pack-my-product-1.2.3The CLI is the trust wedge. The dashboard is where teams pay.
Local pack generation should be easy to try because restricted buyers care about control. Paid plans are for teams that need repeatable release history, approvals, audit trails, dashboard metadata, CI workflows and enterprise deployment controls.
Compare paid workflowRelease history
Keep product/release evidence searchable across versions, buyers and teams.
Team workflow
Use organisations, RBAC, invitations, approval states and reviewer comments.
Audit trail
Record token creation, metadata upload, approvals, billing and security-setting changes.
Governance
Apply policy checks, evidence-upload controls, token expiry and data-handling settings.
CI and dashboard
Upload metadata from GitHub Actions, Azure DevOps or local machines without uploading source code.
Pro and Enterprise
Pro adds higher limits, update history and custom branding; Enterprise adds self-hosted deployment, custom retention and limits, contractual support and onboarding.
The CS Code CLI is ours. Syft and Grype provide the scanner engine.
CS Code wraps release evidence generation, local pack creation, upload boundaries, evidence export, diffing and checksums. Syft generates SBOMs and Grype finds vulnerabilities locally. If those tools are missing, CS Code marks that honestly rather than inventing results.