Skip to content

Security: AvixoSec/codeaxiom

Security

SECURITY.md

Security Policy

CodeAxiom runs commands from task workspaces. Treat every non-local task as untrusted.

Execution rules

  • do not run untrusted repository code on the host machine
  • do not expose host API keys to task environments
  • use disposable containers, VMs, or microVMs before running third-party code
  • prefer network disabled by default
  • use allowlists when network is required for package install
  • set CPU, memory, and time limits
  • save logs outside the task workspace
  • destroy the workspace after the run

Data handling

Private user repositories, traces, logs, patches, prompts, and reports should stay local unless a user explicitly chooses to share them.

Do not use private user runs for training by default.

Secrets

No real secrets should be committed to this repository.

Use .env.local or a platform secret manager for local credentials. .env* files are ignored by default, except example files.

Reporting issues

If you find a security issue in CodeAxiom, email:

contact@avixosec.xyz

Please include:

  • affected file or component
  • reproduction steps
  • impact
  • suggested fix if you have one

Scope

Security reports should focus on the project code, docs, sandbox design, and public site. Do not test third-party services without permission.

There aren't any published security advisories