The extensible, multi-model, unified cybersecurity harness.
🇨🇭 Maintained by the Swiss Applied AI & Cybersecurity Research Lab · 0.security
curl -fsSL https://raw.githubusercontent.com/0sec-labs/0sec/main/install.sh | bash
export PATH="$HOME/.0sec/bin:$PATH"
0 --helpAdd the export line to your shell profile. Configure a model provider,
then run 0 to open the interactive console. Use /run to set up an engagement.
Only test systems you own or have permission to assess.
See Getting started for Docker, source builds, and your first scan.
docs.0.security is the public documentation home for the CLI:
- CLI quickstart and scan workflows.
- Console: interactive investigations and saved conversations.
- Commands, configuration, and API keys.
- Integrations and CI, research workflows, and troubleshooting.
- Verification: how findings are checked and where verification can stop.
- Research: published investigations and upstream fixes.
Docs follow the source checkout; use 0sec --version and command-specific
--help when comparing an installed release with newly documented features.
0cloud and Desktop are not released. Both are in development; their draft guides are not published as user documentation. See the roadmap.
0sec is in active development. Coverage and verification depth vary by workflow; review the evidence before treating a reported issue as confirmed. Generated fixes need review and testing. See the verification guide for prerequisites and limits.
Build instructions and contribution guidelines are in CONTRIBUTING.md. Report security issues through SECURITY.md.
To refresh the command reference after changing CLI registrations:
pnpm --filter '0sec-cli...' build
pnpm docs:sync
pnpm docs:checkThe synchronizer updates usage, arguments, aliases, subcommands, and option
tables without replacing workflow or safety notes. New or removed commands
require a reviewed documentation section; CI rejects missing sections and
stale reference data. Public fork code is not executed by the PR workflow.
Changes on main publish automatically after the docs freshness check and build.
Keep unreleased product guides marked draft: true. They are available to
contributors through the docs development server but excluded from production
pages, search, and the sitemap. Remove draft status only when the product is
released and its onboarding instructions have been verified.
MIT OR Apache-2.0.
