Skip to content

Security: our-ark/genesis

SECURITY.md

Security Policy

Reporting a vulnerability

Please report vulnerabilities through the repository's private GitHub security advisory flow. Do not open a public issue for a suspected credential leak, arbitrary-code-execution path, unsafe deletion, or source-provenance bypass.

Include the affected Genesis commit, operating system, Python version, source type, and the smallest safe reproduction you can provide.

Source trust boundary

An agent body contains executable code. Genesis runs the validation command declared by that body before accepting a birth. Inspect an unfamiliar source before authorizing it, pin remote creation to a reviewed full commit SHA, and use --trust-source only for code you intend to execute. Release tags may be used for inspection, but Genesis does not accept them as the execution boundary because tags can move.

Generated agents are ordinary local repositories. Genesis does not make their code semantically safe, sandbox their future runtime, or protect secrets placed inside their tracked body.

Private state

Credentials, memories, logs, chat identifiers, and instance state must remain outside the body paths declared in genesis.toml. Before publishing either a source body or a generated descendant, audit both its current tree and complete Git history.

There aren't any published security advisories