zephex
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
←BackSign in
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
Get started freeSign in
DocsAPIToolsEditorsChangelogHelp

GET STARTED

WelcomeQuickstartSetup videoMCP Q&A (learn)BlogWhat is MCP?Who is Zephex for?Plans & PricingZ-GASAB benchmarkBenchmark chart (live)Changelog

INSTALLATION

Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Test Pulse (check test)Test Pulse commandsSupply Pulse (supply)Supply Pulse commandsTerminal CLI referenceWeb Terminal (dashboard)Command CompassCLI commandsCLI in DockerCLI: All editors (one command)CLI: Crush, Hermes, ChatGPT, KiloOAuth & HTTP setupInstall overviewHTTP APISetup WalkthroughHTTP vs stdio

API & KEYS

API Key ManagementKey Naming & FormatAuthenticationKey Dashboard

CONFIGURATION

Universal RequirementsSupported EditorsHow It WorksArchitectureCLAUDE.md TemplateAGENTS.md Template

EDITORS28 guides

Supported EditorsVS CodeVS Code extension (Marketplace)Claude CodeCursorWindsurfJetBrains

PLATFORM

macOSWindowsLinux

TOOLS10 tools

Capabilities OverviewTools OverviewTool FilteringTool Workflowsget_project_contextread_codefind_codecheck_packageloop_guardexplain_architectureZephex_dev_infoscope_taskaudit_headerskeep_thinking

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7Zephex vs GitHub MCPZephex vs SmitheryMCP EcosystemMarkdown Access

SUPPORT

Help CenterMCP troubleshootingTeam rolloutFAQConnection IssuesRate LimitsDowntime & ErrorsBillingTier GuidePro & Max guideUsage LimitsUsage Analytics

LEGAL

SecurityData HandlingPrivacy PolicyTerms of Service

Quick Links

API Reference

Complete API documentation

Troubleshooting

Common issues and solutions

Community

Join our Discord community

Plugins

Editor and CLI integrations

Pricing

Free, Pro, and Max plans

Enter
Zephex_devzephex-devzephexzephexhello@zephex.dev
© 2026 Zephex. All systems operational.

Installation

Supply Pulse commands

Copy-paste reference for zephex supply — targets, flags, URL vs repo scans, and session helpers.

Guide: Supply Pulse overview · API key

Aliases

Natural language and short forms route to the same command:

shell
zephex supplyzephex supzephex chain# "secrets" alone → secrets-focused supply scan
Targets
TargetWhat runs
(default) or .Full repo scan in current directory
https://… or example.comLive URL — download public JS bundles, secrets, source maps
. + https://…Repo scan + live URL + cross-reference
github:owner/repoShallow public clone, then repo scan
shell
zephex supplyzephex supply ./backendzephex supply https://staging.example.comzephex supply myapp.comzephex supply . + https://myapp.comzephex supply github:acme/web-app
URL scan flags
shell
# Default URL scan — bundles + secrets + source mapszephex supply https://app.example.com # Secrets in bundles only (faster)zephex supply https://app.example.com --only secrets # Skip retire.js library CVE passzephex supply https://app.example.com --bundle-only # Hide informational noisezephex supply https://app.example.com --severity high
Repo scan flags
shell
# Balanced defaultzephex supply # Single phasezephex supply --only secretszephex supply --only depszephex supply --env-onlyzephex supply --gha-onlyzephex supply --rls-only # CVE reachability (fewer false positives)zephex supply --only deps --reachability # Include devDependencies in CVE scanzephex supply --only deps --include-dev # CI exit code on critical or verified secretszephex supply --only secrets --strict
Output & session
shell
# Machine-readable full resultzephex supply --json # Minimal terminal noisezephex supply -q # Re-print last scan (local cache, ~30m)zephex supply last # Follow-up question on cached scanzephex supply --why "which findings are false positives?"zephex supply --why "explain the Supabase JWT" --refresh # Cloud history (needs API key)zephex supply history

--strict exits with code 1 when critical findings or verified secrets are present — useful in CI.

All flags
FlagPurpose
--jsonFull structured scan result on stdout
--strictNon-zero exit on critical / verified secrets
--quiet / -qSuppress human report formatting
--only secrets|deps|env|gha|rls|urlRun one phase only
--severity critical|high|medium|low|informationalMinimum severity to show
--reachabilityFilter dependency CVEs by code usage (repo)
--include-devInclude devDependencies in CVE scan
--bundle-onlyURL scan: skip JS library CVE pass
--git-history-depth nDeeper clone for github: targets
--why "…"Ask about the last cached scan
--refreshIgnore cache when using --why
Common workflows

Before deploy

shell
zephex supply . + https://production.example.com --strict

Quick homepage check

shell
zephex supply https://www.example.com --severity high

Secrets-only in CI

shell
zephex supply --only secrets --strict --json > supply-report.json

Open source repo

shell
zephex supply github:vercel/next.js --only secrets
Related tools
  • check_package — is this npm package safe to install?
  • audit_headers — HTTP security headers on a live URL (editor MCP)
  • Test Pulse — local test health before ship