Local-first, explicit access, inspectable installs.
Spark should be useful without becoming mysterious. Installers are pinned, secrets stay local, and support reports should never leak tokens.
Security checks users can run.
Local audit
spark security audit
Checks module trust, dangerous patterns, provenance, and local launch risks.
Provenance
spark verify --provenance spark verify --installers --hosted-installers
Confirms the installer and blessed modules match the pinned release chain.
Support bundle
spark support bundle
Creates a redacted local support package. Review before sharing.
Secrets
spark secrets list
Shows secret IDs without printing secret values.
Access levels in normal words.
Talk and remember only
Spark can talk and remember. It should not build or inspect external resources.
Build only when asked
Spark can start missions only after an explicit build request.
Research and build when asked
Recommended. Spark can inspect public links, docs, and repos when asked, and can use Spawner for explicit missions.
Broader local tools
For trusted local use. Spark may use broader operating-system tools, but should still ask before destructive actions.
Share fixes safely.
If Spark Doctor finds a fix that could help other users, it may draft an upstream report or PR candidate. The user must review it before sharing.
Never share
Telegram tokens, API keys, local env files, personal memory, private repo content, or raw logs that have not been reviewed.