Skip to content

Security: arasovic/pi-worker

SECURITY.md

Security

The supported release is the latest published version. Releases have always moved forward from the previous one since v0.1.x; no release has ever been a backport to an older line.

Workers execute bash with the current user's permissions in the current writable workspace. Pi Worker is not a sandbox.

Every run keeps each worker's Pi session transcript in its run directory (worker-<n>/, mode 0700) unless it was started with --no-transcript. The transcript is not redacted: it holds the full prompt including --data, tool arguments and results, the contents of files the worker read (.env included), shell output and thinking. Do not paste a transcript into a report or an issue. pi-worker never deletes one on its own; runs prune removes it with its run.

Do not post credentials, Pi profiles, provider configuration, prompts, workspace contents, or sensitive logs in public issues. Do not disclose a vulnerability publicly.

Use GitHub private vulnerability reporting. If that channel is unavailable, do not disclose publicly or send secrets elsewhere. Publication requires the private reporting channel to be enabled first.

There aren't any published security advisories