Skip to content
workspaceguardrails
  • Home
  • Open Source[4]
  • System Policies[0]
  • Git Hooks[21]
  • Anti-Patterns[293]
  • Hook Configs[20]
  • Sandbox Configs[27]
  • Tools & Scripts[14]
  • AI Governance[20]
  • LLM Gateway
  • Static Analysis
  • Playground
  • Integration Guide
  1. Home
  2. Sandbox Configs
    The Digital and AI Workspace Guardrails Platform2026 ◆ Independent AI Labs
    Skip to content
    workspaceguardrails
    • Home
    • Open Source[4]
    • System Policies[0]
    • Git Hooks[21]
    • Anti-Patterns[293]
    • Hook Configs[20]
    • Sandbox Configs[27]
    • Tools & Scripts[14]
    • AI Governance[20]
    • LLM Gateway
    • Static Analysis
    • Playground
    • Integration Guide
    1. Home
    2. Sandbox Configs
      The Digital and AI Workspace Guardrails Platform2026 ◆ Independent AI Labs
      Skip to content
      workspaceguardrails
      • Home
      • Open Source[4]
      • System Policies[0]
      • Git Hooks[21]
      • Anti-Patterns[293]
      • Hook Configs[20]
      • Sandbox Configs[27]
      • Tools & Scripts[14]
      • AI Governance[20]
      • LLM Gateway
      • Static Analysis
      • Playground
      • Integration Guide
      1. Home
      2. Sandbox Configs

        Sandbox Configs

        Guard policy configurations from the sibling WORKSPACE-GUARD repository. The guard tree is a soft dependency; configs appear here when available.

        27 of 27 guard policies

        ambient-allowlist

        Ambient capability grants for git-guard workloads in capability mode.

        Binary Guard

        ambient-allowlist.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        banned_words_exceptions

        Exceptions to the banned-words scan.

        Quality Gates

        banned_words_exceptions.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        binary_guard_policy_rules

        Full GTFOBins coverage rules for SUID/file-capability binaries, host-independent.

        Binary Guard

        binary_guard_policy_rules.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        cap-allowlist

        Per-path file-capability allowlist restricted to system binaries.

        Binary Guard

        cap-allowlist.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        coverage_thresholds

        Test coverage thresholds enforced by the coverage no-devolution check.

        Quality Gates

        coverage_thresholds.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        dead_code

        Configuration for dead code detection (lib/checks_dead_code.sh).

        Quality Gates

        dead_code.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        dependency_excludes

        Dependencies excluded from dependency auditing.

        Quality Gates

        dependency_excludes.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        duplicate_dependency_excludes

        Dependencies intentionally declared in both workspace root and members, not flagged as redundant.

        Quality Gates

        duplicate_dependency_excludes.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        file_length_limits

        Maximum allowed lines per file enforced by the file-length check.

        Quality Gates

        file_length_limits.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        git_guard_attack_surface_matrix

        Exhaustive destructive-git attack surface derived from git.git source, used for coverage audits.

        Git Guard

        git_guard_attack_surface_matrix.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        git_guard_config_keys

        Dangerous git config key glob patterns and sudo-gated keys blocked by the guard.

        Git Guard

        git_guard_config_keys.yaml

        Dangerous git config key glob patterns and sudo-gated keys blocked by the guard.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        dangerouslist<string>Required

        Glob patterns for git config keys that are unconditionally blocked for all users. Patterns use * (single segment) and ** (multi-segment) wildcards.

        Current: [HOVER TO SHOW VALUE]
        sudo_gatedlist<string>Required

        Git config keys blocked for non-root users only (e.g. user.email, core.editor). Root users may set these.

        Current: [HOVER TO SHOW VALUE]
        value_taking_optslist<string>Required

        Git config CLI options that consume the next argument as a value (used by the positional-key scanner to skip values).

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        git_guard_environment

        Environment variable policy: allowed vars, sudo-gated vars, and blocked hook-bypass vars.

        Git Guard

        git_guard_environment.yaml

        Environment variable policy: allowed vars, sudo-gated vars, and blocked hook-bypass vars.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        allowedlist<string>Required

        Environment variables allowed through the sanitized execve env to real git (e.g. HOME, USER, LANG).

        Current: [HOVER TO SHOW VALUE]
        sudo_gated_identitylist<string>Required

        Git identity env vars gated to root. Non-root users have these dropped/ignored (e.g. GIT_AUTHOR_NAME, GIT_COMMITTER_EMAIL).

        Current: [HOVER TO SHOW VALUE]
        sudo_gated_editorlist<string>Required

        Git editor env vars gated to root. Non-root users have these dropped/ignored (e.g. EDITOR, GIT_EDITOR).

        Current: [HOVER TO SHOW VALUE]
        blocked_bypasslist<string>Required

        Hook-bypass env vars that are blocked when set to a non-empty value (e.g. SKIP, PRE_COMMIT_ALLOW_NO_CONFIG).

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        git_guard_policy_matrix

        Table-driven expected outcomes for git-guard policy enforcement tests.

        Git Guard

        git_guard_policy_matrix.yaml

        Table-driven expected outcomes for git-guard policy enforcement tests.

        versionintegerRequiredDefault: 1

        Schema version.

        Current: [HOVER TO SHOW VALUE]
        caseslist<object>Required

        Policy test cases: argv vectors with expected block/allow outcome.

        Current: [HOVER TO SHOW VALUE]
        cases[].idstringRequired

        Stable case identifier for test output.

        cases[].argvlist<string>Required

        Full argv vector starting with 'git'.

        cases[].expectstringRequired

        Expected outcome: blocked or allowed.

        cases[].reason_containsstringOptional

        Substring expected in block reason (blocked cases only).

        cases[].sudo_onlybooleanOptionalDefault: false

        When true, case runs only when guard detects sudo/AT_SECURE context.

        Share feedback

        You voted thumbs down

        git_guard_protected_branches

        Protected branch names and prefixes that require --ff-only/--rebase for pull and merge.

        Git Guard

        git_guard_protected_branches.yaml

        Protected branch names and prefixes that require --ff-only/--rebase for pull and merge.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        brancheslist<string>Required

        Branch names (case-insensitive) that require --ff-only or --rebase for pull/merge operations (e.g. main, master, develop).

        Current: [HOVER TO SHOW VALUE]
        prefixeslist<string>Required

        Branch name prefixes (case-insensitive) that require --ff-only or --rebase for pull/merge operations (e.g. release/).

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        git_guard_resource_limits

        Resource limit thresholds and contract-check timing parameters.

        Git Guard

        git_guard_resource_limits.yaml

        Resource limit thresholds and contract-check timing parameters.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        nofileintegerRequiredDefault: 256

        Maximum number of open file descriptors (RLIMIT_NOFILE) for the guard and child git process.

        Current: [HOVER TO SHOW VALUE]
        coreintegerRequiredDefault: 0

        Core dump limit (RLIMIT_CORE). 0 disables core dumps.

        Current: [HOVER TO SHOW VALUE]
        contract_timeout_msintegerRequiredDefault: 2000

        WORKSPACE-CI contract check kill timeout in milliseconds. The contract check child is SIGKILLed after this duration.

        Current: [HOVER TO SHOW VALUE]
        contract_poll_msintegerRequiredDefault: 50

        Contract check poll interval in milliseconds. The guard sleeps this long between waitpid(WNOHANG) retries.

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        git_guard_subcommands

        Git subcommand policy: which subcommands are blocked, partially blocked, or require contract checks.

        Git Guard

        git_guard_subcommands.yaml

        Git subcommand policy: which subcommands are blocked, partially blocked, or require contract checks.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        blockedlist<string>Required

        Git subcommands unconditionally denied for all users (e.g. reset, clean, update-ref plumbing).

        Current: [HOVER TO SHOW VALUE]
        sudo_gatedlist<string>OptionalDefault: []

        Git subcommands denied for non-root, allowed in sudo/AT_SECURE context (e.g. checkout, switch, submodule).

        Current: [HOVER TO SHOW VALUE]
        partiallist<string>Required

        Git subcommands subject to conditional/flag-based blocking (e.g. push with --force, stash drop).

        Current: [HOVER TO SHOW VALUE]
        contract_checklist<string>Required

        Git subcommands that must pass WORKSPACE-CI quality gates before execution (e.g. commit, push).

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        git_ssh_allowlist

        SSH destinations the git-ssh-wrapper may connect to; everything else is refused.

        Git Guard

        git_ssh_allowlist.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        home-lock-users

        Fleet UNIX users provisioned with per-user git identity and SSH keys. Live file config/home-lock-users.yaml is gitignored; commit home-lock-users.yaml.example only.

        Host Hardening

        home-lock-users.yaml

        Fleet UNIX users provisioned with per-user git identity and SSH keys. Live file config/home-lock-users.yaml is gitignored; commit home-lock-users.yaml.example only.

        versionintegerRequiredDefault: 1

        Current: [HOVER TO SHOW VALUE]
        userslist<object>Required

        Login users that receive root-provisioned identity and SSH material.

        Current: [HOVER TO SHOW VALUE]
        users[].namestringRequired

        UNIX account name (must exist in /etc/passwd before provision).

        users[].git_namestringRequired

        git user.name injected by the guard for this account.

        users[].git_emailstringRequired

        git user.email injected by the guard for this account.

        Share feedback

        You voted thumbs down

        host-provision

        Host bootstrap: admin break-glass, fleet sudo audit, guard stack. Live file config/host-provision.yaml is gitignored; commit host-provision.yaml.example only.

        Host Hardening

        host-provision.yaml

        Host bootstrap: admin break-glass, fleet sudo audit, guard stack. Live file config/host-provision.yaml is gitignored; commit host-provision.yaml.example only.

        versionintegerRequiredDefault: 1

        Current: [HOVER TO SHOW VALUE]
        user_management
        Current: [HOVER TO SHOW VALUE]
        user_management.enabledbooleanRequiredDefault: true

        When false, skip admin/sudo phases; install-guard-host-exec gate disabled.

        admin
        Current: [HOVER TO SHOW VALUE]
        admin.namestringRequiredDefault: admin

        admin.shellstringOptionalDefault: /bin/bash

        admin.create_homebooleanOptionalDefault: true

        admin.git_namestringRequired

        admin.git_emailstringRequired

        fleet_users_filestringRequiredDefault: config/home-lock-users.yaml

        Current: [HOVER TO SHOW VALUE]
        guard_stack
        Current: [HOVER TO SHOW VALUE]
        guard_stack.install_lockbooleanOptionalDefault: false

        guard_stack.install_auditdbooleanOptionalDefault: false

        Share feedback

        You voted thumbs down

        sensitive_files_exceptions

        Safe exceptions to the sensitive-files commit block.

        Quality Gates

        sensitive_files_exceptions.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        shared_host_profiles

        Hostname to git deployment class mapping; install targets assert the host before mutating the system.

        Shared

        shared_host_profiles.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        shared_locked_paths

        Locked path policy: which files and directory trees the guard locks to root:root in capability mode.

        Shared

        shared_locked_paths.yaml

        Locked path policy: which files and directory trees the guard locks to root:root in capability mode.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        recursive_tree_pathslist<string>Required

        Paths (relative to repo root) whose entire directory tree is locked recursively. Directories → 0o755, regular files → 0o644, hook files under hooks/ → 0o755.

        Current: [HOVER TO SHOW VALUE]
        recursive_tree_glob_patternslist<string>Required

        Directory-name glob patterns. Every directory in the repo tree whose name matches the glob is recursively locked. Dirs → 0o755, files → 0o644.

        Current: [HOVER TO SHOW VALUE]
        individual_file_pathsmap<string,integer>Required

        Individual file paths (relative to repo root) to lock with an explicit octal mode. Key = relative path, value = octal mode (e.g. 0o644).

        Current: [HOVER TO SHOW VALUE]
        glob_patternsmap<string,integer>Required

        Filename-only glob patterns. Every file in the repo tree whose name matches the pattern is locked with the given octal mode. Key = glob pattern, value = octal mode (e.g. 0o644).

        Current: [HOVER TO SHOW VALUE]
        absolute_file_pathsmap<string,integer>OptionalDefault: {}

        Absolute paths (with an optional leading ~ for the current user $HOME, or a literal /root/ path for root) of files OUTSIDE the repo tree that the home-lock program chowns to root:root and mode-sets. Covers ~/.gitconfig, ~/.config/git/config, ~/.gitconfig.local, ~/.ssh/authorized_keys, ~/.ssh/config, plus /root/ equivalents. Private id_* keys and shell rc files are deliberately NOT listed. Key = absolute or ~ -prefixed path, value = octal mode (e.g. 0o644 for gitconfig, 0o600 for authorized_keys).

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        shared_paths

        Filesystem paths and path patterns used by the guard for logging, child PATH, scripts, and workspace detection.

        Shared

        shared_paths.yaml

        Filesystem paths and path patterns used by the guard for logging, child PATH, scripts, and workspace detection.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        log_filestringRequiredDefault: .workspace-guard.log

        Per-user block/warn log filename. Joined onto the user's $HOME directory.

        Current: [HOVER TO SHOW VALUE]
        child_pathstringRequiredDefault: /usr/local/bin:/usr/bin:/bin

        PATH value passed to child git and bash processes. Centralized to eliminate duplication across call sites.

        Current: [HOVER TO SHOW VALUE]
        contract_scriptstringRequiredDefault: projects/CI/lib/checks_quality.sh

        WORKSPACE-CI quality gate script path, relative to the workspace root.

        Current: [HOVER TO SHOW VALUE]
        enforcement_configstringRequiredDefault: workspace/config/project_enforcement.yaml

        Project enforcement YAML path, relative to the workspace root. Used for vendored-tier bypass detection.

        Current: [HOVER TO SHOW VALUE]
        workspace_markerslist<string>Required

        Paths checked to identify the workspace root. All must exist for a directory to be recognized as the workspace root.

        Current: [HOVER TO SHOW VALUE]

        Share feedback

        You voted thumbs down

        shell_guard_policy

        Shell-guard deny policy: a flat table of {id, regex, hint} patterns matched against raw command text.

        Shell Guard

        shell_guard_policy.yaml

        Shell-guard deny policy: a flat table of {id, regex, hint} patterns matched against raw command text.

        versionintegerRequiredDefault: 1

        Schema version. Bumped when the YAML shape changes.

        Current: [HOVER TO SHOW VALUE]
        patternslistRequired

        Ordered pattern table. The FIRST matching entry is the reported rule, so specific patterns precede bare command names they contain.

        Current: [HOVER TO SHOW VALUE]
        patterns[].idstringRequired

        Stable rule identifier used in block messages, audit log lines, and the policy matrix (e.g. suppress-pipe).

        patterns[].regexstringRequired

        Bytes-regex matched unanchored against the raw command text. Connector context is spelled in the pattern (e.g. a leading pipe). Must compile as a regex::bytes::Regex.

        patterns[].hintstringRequired

        Remediation hint printed in the block message and audit log for this rule.

        Share feedback

        You voted thumbs down

        shell_guard_policy_matrix

        Expected block/allow outcomes consumed by the shell-guard policy matrix tests.

        Shell Guard

        shell_guard_policy_matrix.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        silent_swallow_exceptions

        Exceptions to the error-swallowing pattern scan.

        Quality Gates

        silent_swallow_exceptions.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        system-deps

        System dependencies for WORKSPACE-GUARD, checked and installed by make init / make init-check.

        Host Hardening

        system-deps.yaml

        No schema file found.

        Share feedback

        You voted thumbs down

        The Digital and AI Workspace Guardrails Platform2026 ◆ Independent AI Labs