Security posture with operational controls
Trust claims map directly to runtime code paths, validation checks, and observable status surfaces.
Secure defaults snapshot
Unsafe capabilities are opt-in and bounded by explicit configuration contracts.
Raw CDP controls disabled
Direct low-level capabilities require explicit enablement before execution.
Non-local endpoints restricted
Network boundaries prioritize local-only operation unless intentionally configured.
Unsafe export paths blocked
Sanitization and guardrails are defaulted to safe behavior.
Relay, token, and origin controls
Connection channels enforce explicit checks before accepting command traffic.
Secure defaults
Unsafe transport and raw CDP options are disabled by default.
Relay and origin controls
Token checks and origin policy gate extension relay channels.
Data redaction
Sensitive values are redacted from logs and diagnostics outputs.
Reliability posture
Coverage guardrails and deterministic checks back release confidence.
Operational recovery
Status surfaces and reconnect controls support production operations.
Control boundaries
Host and capability constraints isolate risky execution paths.
Data redaction and reliability
Production operations require both privacy discipline and deterministic failure handling.
Data redaction handling
Sensitive values are filtered before diagnostics and exported artifacts are surfaced.
Reliability and testing posture
Release checks enforce build, lint, type, and coverage confidence before publication.
Operational references
Each trust claim is mapped to concrete code and documentation references.
src/config.ts
Source path used to validate controls and operational behavior claims.
src/relay/relay-server.ts
Source path used to validate controls and operational behavior claims.
docs/CLI.md
Source path used to validate controls and operational behavior claims.
docs/TROUBLESHOOTING.md
Source path used to validate controls and operational behavior claims.
vitest.config.ts
Source path used to validate controls and operational behavior claims.
docs/SURFACE_REFERENCE.md
Source path used to validate controls and operational behavior claims.
Review the full security model
Open the security anchor in docs for implementation-level details and operational procedures.