Skip to main content
← Back to list
01Issue
BugOpenSwamp CLI
AssigneesNone

Relationships

#576 vault guide promotes inline secret values (KEY=VALUE) as a primary "swamp vault put" example

Opened by bixu · 6/6/2026

Summary

.claude/skills/swamp/references/vault/guide.md (as written by swamp repo upgrade v20260605) shows inline KEY=VALUE examples for storing secrets as a primary option, with the warning relegated to a parenthetical label. Copy-pasted examples leak the literal values into shell history, sudoers logs, and process tables.

Affected section

Store Secrets (~line 118-122):

**Inline value (appears in shell history):**

swamp vault put dev-secrets API_KEY=sk-1234567890 --json
swamp vault put prod-secrets DB_PASSWORD=secret123 -f --json  # Skip confirmation

The safer piped/interactive variants follow afterwards but aren't presented as the default.

Suggested fix

Lead with --stdin / piped and interactive variants. Demote the inline form to an anti-pattern (or remove it entirely) with an explicit "do not use for real secrets" callout.

Detected by

hivemq/hivemq-pi-review-action@v1 (gpt-5.5) flagged this as severity HIGH on hivemq/swamp-extensions#103.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

6/6/2026, 12:43:39 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

bixu commented 6/6/2026, 1:12:43 PM

Additional location of the same class of bug in v20260605: .claude/skills/swamp/references/vault/references/troubleshooting.md line ~49-51 recommends echo $AWS_ACCESS_KEY_ID; echo $AWS_SECRET_ACCESS_KEY as a credential check. Patched downstream in hivemq/swamp-extensions#103 by switching to presence-only test -n "${VAR:-}" checks; please apply equivalent fix upstream so the next swamp repo upgrade doesn't re-introduce.

Sign in to post a ripple.