You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,3 +16,35 @@ Please do not open a public issue for a suspected vulnerability. Email the maint
16
16
## Secret Handling
17
17
18
18
Never commit API keys, Telegram tokens, OAuth credentials, database files, `.env` files, or local user exports. Use `.env.example` for placeholders only.
19
+
20
+
Secrets are redacted on a best-effort basis (`redactText`/`redactObject` in `src/core/engine.ts`) before commands, history, and logs are persisted. This targets common token shapes and `NAME=value` credential assignments — it is not a guarantee that no secret will ever reach a log file.
21
+
22
+
## Threat Model
23
+
24
+
Setupr runs real shell commands on your machine with your full user privileges. The command-safety
25
+
layer (`src/agent/safety.ts`) is a **best-effort, defense-in-depth guard, not a sandbox.** It
26
+
classifies each planned command and decides whether to allow, confirm, or block it:
27
+
28
+
-**Block (cannot be bypassed by `--force`)** — clearly destructive or hostile patterns such as
0 commit comments