SafeRelay DevSec for VS Code

A SafeRelay.ai product

100% Local. Zero-Knowledge. Your secrets never leave your machine.

SafeRelay DevSec is a VS Code extension that redacts secrets, PII, and sensitive data from your files and AI prompts — entirely on your machine, with no network calls, no telemetry, and no cloud processing of any kind.

The Trust Question — Answered Up Front

Every DLP tool that touches your secrets has to answer one question:

Where does the data go when you restore a tokenized file back to its real values?

SafeRelay DevSec's answer: nowhere.

The mapping between [OPENAI_KEY_1] and sk-proj-abc123... lives in RAM only — inside your VS Code process — for the duration of your session. It is never written to disk, never sent to a server, never stored in VS Code's globalState or workspaceState, and never logged. When VS Code closes, the vault is gone.

This is what zero-knowledge actually means in practice. SafeRelay's servers, if they ever exist in your workflow, will only ever see encrypted ciphertext — never your plaintext secrets.

What It Does

1. Sanitize a file (YAML, JSON, env, logs, config, code) → SafeRelay scans it locally, replaces secrets with typed placeholders ([OPENAI_KEY_1], [IP_1], [AWS_SECRET_1]), and writes a .redacted copy alongside the original.
2. Share the redacted file freely — to an AI, a colleague, a Slack thread, a GitHub issue. It contains no real secrets.
3. Restore the AI's response (or the file) → SafeRelay swaps every placeholder back with the original value from the in-memory vault. The full round-trip happens without your secrets ever appearing in chat, logs, or a third-party system.

Commands

All commands are also accessible via Ctrl+Shift+P → type "SafeRelay".

The Sanitize → AI → Restore Workflow

config.yaml          →  [Sanitize File]  →  config.redacted.yaml
                                              ↓
                                         Send to AI / colleague / Slack
                                              ↓
                                         AI edits it, returns modified version
                                              ↓
                          [Restore File]  →  config.restored.yaml  ← real values back

Example — before sanitize:

api_key: sk-proj-abc123def456ghi7890jklmnopqrstuvwxyz
db_host: 192.168.1.100
DB_URL=postgres://admin:s3cr3t@10.0.0.5:5432/prod
token: ghp_ABCdef1234567890xyzABCdef123456789012

After sanitize (config.redacted.yaml):

api_key: [OPENAI_KEY_1]
db_host: [IP_1]
DB_URL=[ENV_VALUE_1]
token: [GITHUB_PAT_1]

After restore — original values are back exactly as they were.

What Gets Redacted

Free — DevSec Shield

Pro — Additional Shields

Status Bar

The $(shield) SafeRelay item shows on the right of the status bar.

• No vault entries: $(shield) SafeRelay
• Vault active: $(shield) SafeRelay (4) — 4 secrets stored in RAM
• Click → Quick Menu with all actions

Settings

Configure shields interactively via Ctrl+Shift+Alt+G → Configure Shields — no need to edit JSON.

Security & Privacy Posture

Why RAM-only is acceptable

The threat model for an in-memory vault is identical to having the file open in your editor — an attacker who can dump your VS Code process memory already has access to the file on disk. RAM-only means no persistence risk: no stolen laptop scenario, no log exfiltration, no cloud breach.

Roadmap

Team Vault — How it will work (zero-knowledge)

Senior Dev machine:
  sanitizeFile() → vault entries encrypted with team key (client-side)
                 → encrypted blob synced to SafeRelay.ai servers
                 → server sees: { "abc123": "<ciphertext>" }  ← never plaintext

Junior Dev machine:
  receives redacted file via Slack
  → extension fetches encrypted blob
  → decrypts locally with team key
  → restoreFile() works exactly as today

SafeRelay's servers handle routing and storage of encrypted blobs only. They cannot decrypt vault entries. This is the 1Password / Bitwarden architecture.

Manual Test

npm install
npm run compile

1. Open this folder in VS Code → press F5 → Extension Development Host opens
2. Ctrl+, → search "saferelay" → set enabled to true
3. Create a test file with:

api_key: sk-proj-abc123def456ghi7890jklmnopqrstuvwxyz
db_host: 192.168.1.100
DB_URL=postgres://user:password@10.0.0.5:5432/prod
token: ghp_ABCdef1234567890xyzABCdef123456789012

4. Right-click the file → SafeRelay: Sanitize File → click View Diff
5. Confirm secrets are replaced. Status bar shows $(shield) SafeRelay (4)
6. Copy the contents of the .redacted file
7. Run SafeRelay: Restore Clipboard → paste → original values are back
8. Right-click the .redacted file → SafeRelay: Restore File → .restored file matches original

About SafeRelay.ai

SafeRelay DevSec is built by SafeRelay.ai — privacy-first security tooling for developers, DevOps, and enterprise teams.

License: UNLICENSED — Private. Not for redistribution.