Bagel

Inventory what matters on developer machines—tools, configs, and metadata about secrets—to improve org supply‑chain security without exfiltrating payloads.

What is it?

Bagel is a cross‑platform CLI that inspects developer workstations (macOS, Linux, Windows) and produces a structured report of:

• Dev tool configurations and risky settings across 9 probes: Git, SSH, npm, environment variables, shell history, cloud credentials (AWS/GCP/Azure), JetBrains IDEs, GitHub CLI, and AI CLI tools.
• Secret locations (metadata only): presence of tokens, keys, and credentials in config files, env vars, and history—detected by 8 secret detectors—never the secret values.

For detailed documentation on each probe and detector, see the Bagel docs site.

Looking for more? If you want a more powerful, enterprise-grade version with the ability to deploy at scale and collect posture information across your entire developer laptop fleet, have a look at the BoostSecurity Developer Endpoint Protection (DEP) product.

Privacy & Safety by Design

• No payloads. Ever. Bagel records only metadata (path, owner, perms, timestamps, config flags, key type/length/expiry). Secret values are never included in output or written to disk.
• Local‑first. Reports are printed to stdout as JSON by default.
• Minimally intrusive. Read‑only operations; no process injection; no network scanners.
• Transparent. Every probe is documented and can be toggled via configuration.

Why run it?

Modern supply‑chain risk often lands on developer endpoints (malicious packages, misconfig creds, weak key hygiene). Bagel standardizes visibility so security teams can:

• Find high‑signal misconfigs (e.g., http.sslVerify=false, ForwardAgent yes, plaintext creds files, unencrypted SSH keys).
• Detect leaked secrets in shell history, .env files, and config files.
• Enforce baseline posture checks in CI with --strict.

Risk checks (examples)

• Git: credential.helper=store, http.sslVerify=false, custom core.sshCommand with non‑standard binaries, dangerous protocols, fsck disabled.
• npm: tokens in .npmrc, strict-ssl=false, HTTP (non‑HTTPS) registries.
• SSH: keys without passphrase, ForwardAgent yes, StrictHostKeyChecking=no, permissive file modes.
• Environment & history: secrets embedded in env vars, .env files, or shell command history.
• Cloud: AWS credentials, GCP API keys, Azure storage keys in config files.

Installation

Pre-built Binaries

Download the latest release from GitHub Releases.

macOS:

# Intel Mac
curl -sL https://github.com/boostsecurityio/bagel/releases/latest/download/bagel_Darwin_x86_64.tar.gz | tar xz
sudo mv bagel /usr/local/bin/

# Apple Silicon
curl -sL https://github.com/boostsecurityio/bagel/releases/latest/download/bagel_Darwin_arm64.tar.gz | tar xz
sudo mv bagel /usr/local/bin/

Homebrew:

brew install bagel

Linux:

# x86_64
curl -sL https://github.com/boostsecurityio/bagel/releases/latest/download/bagel_Linux_x86_64.tar.gz | tar xz
sudo mv bagel /usr/local/bin/

# ARM64
curl -sL https://github.com/boostsecurityio/bagel/releases/latest/download/bagel_Linux_arm64.tar.gz | tar xz
sudo mv bagel /usr/local/bin/

Windows:

Download bagel_Windows_x86_64.zip from the releases page, extract it, and add it to your PATH.

Invoke-WebRequest -Uri "https://github.com/boostsecurityio/bagel/releases/latest/download/bagel_Windows_x86_64.zip" -OutFile "bagel.zip"
Expand-Archive -Path "bagel.zip" -DestinationPath "."

Build from Source

Requires Go 1.25 or later.

git clone https://github.com/boostsecurityio/bagel.git
cd bagel
go build -o bagel ./cmd/bagel

Verify Installation

bagel version

Usage

bagel scan

This scans your workstation and outputs findings to stdout in JSON format.

Common flags

Examples

# Save report to a file
bagel scan -o report.json

# Table output for quick review
bagel scan -f table

# CI gate: fail the build if findings exist
bagel scan --strict

# Debug a specific scan
bagel scan --verbose --no-progress

Configuration

Bagel uses a YAML configuration file. It looks for bagel.yaml in these locations (in order):

1. Path specified with --config
2. Current directory (./bagel.yaml)
3. Platform config directory (~/.config/bagel/bagel.yaml on Unix, %APPDATA%\bagel\bagel.yaml on Windows)

Example configuration

version: 1
probes:
  git:
    enabled: true
  ssh:
    enabled: true
  npm:
    enabled: true
  env:
    enabled: true
  shell_history:
    enabled: true
  cloud:
    enabled: true
  jetbrains:
    enabled: true
  gh:
    enabled: true
  ai_credentials:
    enabled: true
  ai_chats:
    enabled: true
privacy:
  redact_paths: []
  exclude_env_prefixes: []
output:
  include_file_hashes: false
  include_file_content: false

All probes are enabled by default. To disable a probe, set enabled: false.

Version check telemetry

By default, bagel reaches out at most once every 24 hours to check whether a newer release is available. The request reports the current bagel version, an anonymous instance identifier persisted under the platform config directory (~/.config/bagel/version-check.yaml on Unix, %APPDATA%\bagel\version-check.yaml on Windows), and a count of CLI invocations since the last check. No scan, host, or finding data is sent. To disable, use any of:

• --disable-version-check flag
• BAGEL_DISABLE_VERSION_CHECK=1 environment variable
• disable_version_check: true in bagel.yaml

Output schema (excerpt)

{
  "metadata": {
    "version": "0.1.0",
    "timestamp": "2026-02-10T12:00:00Z",
    "duration": "1.234s"
  },
  "host": {
    "hostname": "dev-laptop",
    "os": "darwin",
    "arch": "arm64",
    "username": "dev",
    "system": {
      "os_version": "15.3",
      "kernel_version": "Darwin 25.2.0",
      "cpu_model": "Apple M1",
      "cpu_cores": 8,
      "ram_total_gb": 16
    }
  },
  "findings": [
    {
      "id": "git-ssl-verify-disabled",
      "probe": "git",
      "severity": "high",
      "title": "Git SSL Verification Disabled",
      "message": "Git is configured to skip SSL certificate verification...",
      "path": "git-config:http.sslverify"
    },
    {
      "id": "ssh-private-key-rsa",
      "probe": "ssh",
      "severity": "critical",
      "title": "Unencrypted SSH Private Key Detected (RSA)",
      "message": "An unencrypted RSA SSH private key was detected...",
      "path": "file:/Users/dev/.ssh/id_rsa"
    }
  ]
}

Architecture

• Probes: small, hermetic modules that scan specific areas of the system.
• Detectors: reusable secret detection patterns used by probes.
• Collector: orchestrates probes with timeouts and resource caps.
• Reporters: render JSON or table output; emit exit codes for CI.

Each probe declares its scope (user/system), paths touched, env vars read, and risk rules it can emit.

Current Probes

Current Detectors

Platform support

All probes work cross-platform with appropriate path handling for each OS.

Scrub Command

Fork addition -- not in upstream Bagel.

bagel scrub removes credentials from AI CLI session logs and shell history files, replacing them with [REDACTED-<type>] markers while preserving conversation context.

# Scan and interactively confirm (default)
bagel scrub

# Skip prompt, apply immediately
bagel scrub --yes

# Scan only, no modifications
bagel scrub --dry-run

# Scrub without grace period (includes recent files)
bagel scrub --yes --grace-minutes 0

# Scrub a single file
bagel scrub --yes --file ~/.claude/projects/foo/abc123.jsonl

Targets: - ~/.claude/projects/**/*.jsonl -- Claude Code session logs - ~/.claude/projects/**/*.txt -- Claude Code tool results - ~/.codex/sessions/**/*.jsonl -- Codex CLI session logs - ~/.gemini/tmp/*/chats/*.json -- Gemini CLI chat logs - ~/.local/share/opencode/**/*.json -- OpenCode session logs - ~/.bash_history -- Bash shell history - ~/.zsh_history -- Zsh shell history - ~/.sh_history -- Generic shell history - ~/.local/share/fish/fish_history -- Fish shell history

Recommended workflow: 1. bagel scan -f table -- assess your exposure 2. bagel scrub --yes -- clean up 3. bagel scan -f table -- verify reduction 4. Rotate any credentials that were found

Integrations

• CI: run bagel scan --strict in your pipeline to fail builds when findings are detected.
• Fleet-wide deployment: for enterprise-grade deployment at scale with centralized posture reporting across your developer laptop fleet, see BoostSecurity DEP.

Exit codes

• 0 – success, no findings detected (or --strict not set)
• 1 – runtime error
• 2 – findings detected (when using --strict)

FAQ

Does it read my secrets? No. It only gathers metadata and security‑relevant flags.

Is it noisy? Probes are read‑only, batched, and time‑boxed to keep scans under a minute on typical dev machines.