Pepper SAST documentation

AI-powered static application security testing (SAST) for your organization. This guide covers installation, day-to-day usage, and every settings screen in the web UI.

What Pepper does

Pepper scans source code for security issues using multiple engines: pattern-based and LLM-assisted SAST, secret detection, software composition analysis (SCA), infrastructure-as-code checks, and optional zero-day-style logic analysis. Results appear as findings with severity, remediation guidance, compliance mapping, and optional GitHub fix pull requests.

Architecture (high level)

Main navigation (sidebar)

Menu itemRoutePurpose
Dashboard/dashboardOrg overview, stats, quick actions
New Scan/scans/newStart a scan from Git URL, upload, or SVN
Projects/projectsProjects, grades, finding counts
Repositories/repositoriesGitHub OAuth, import or manual repo URL

Settings (sidebar section)

SettingRouteDocumentation
LLM Config/settings/llmLLM config
Policies/settings/policiesSecurity policies
Build Gates/settings/build-gatesBuild gates
Team/settings/teamTeam & roles
Integrations/settings/integrationsGitHub, webhooks, CI

Scan types

TypeWhat runs
FULLSAST (pattern or LLM), SCA, secrets, IaC, zero-day (if LLM SAST enabled)
SAST_ONLYStatic analysis only
SCA_ONLYDependency / supply-chain only
SECRETS_ONLYSecret scanning only
INCREMENTALReserved for delta scans (limited support)

Source types

SourceHow it works
GIT_CLONEClone from HTTPS URL; optional token or org GitHub OAuth token for private repos
UPLOADZip/tar archive uploaded to MinIO and extracted on the worker
SVN_CHECKOUTSubversion checkout (requires svn on worker)
WEBHOOKTriggered by GitHub/GitLab push or MR events

Documentation map

Getting started

Install dependencies, configure .env, seed database, run app + worker, first login.

How to use Pepper

Projects, scans, findings, GitHub repositories, open fix PR, compliance export, notifications.

Settings reference

Every settings screen: fields, behavior, and API endpoints.

Environment variables

Complete .env reference for local and Docker deployments.

Open these HTML files in a browser from the docs/ folder, or serve with npx serve docs for local browsing.