8000 gravity/SECURITY.md at main · dominicletz/gravity · GitHub
[go: up one dir, main page]

Skip to content
{"props":{"color_mode":"dark","logged_in":false,"marketing_page":false,"home_path":"/","login_path":"/login?return_to=https%3A%2F%2Fgithub.com%2Fdominicletz%2Fgravity%2Fblob%2Fmain%2FSECURITY.md","signup_path":"/signup?ref_cta=Sign+up\u0026ref_loc=header+logged+out\u0026ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fblob%2Fshow\u0026source=header-repo\u0026source_repo=dominicletz%2Fgravity","signup_enabled":true,"is_signup_controller":false,"show_search_and_nav":true,"hide_search":false,"private_mode_enabled":false,"should_use_dotcom_links":true,"auth_hydro_click":"{\"event_type\":\"authentication.click\",\"payload\":{\"location_in_page\":\"site header menu\",\"repository_id\":null,\"auth_type\":\"SIGN_UP\",\"originating_url\":\"https://github.com/dominicletz/gravity/blob/main/SECURITY.md\",\"user_id\":null}}","auth_hydro_click_hmac":"15c666e3af25978c38addee362ebee052a98f08ac253dfdb75d2cfcbb8a22cad"}}

Latest commit

 

History

History
28 lines (20 loc) · 1.31 KB

SECURITY.md

File metadata and controls

28 lines (20 loc) · 1.31 KB

Security policy

Reporting a vulnerability

Use GitHub private vulnerability reporting to report a suspected vulnerability privately to the repository maintainers. Do not open a public issue containing exploit details or credentials.

Include the affected version, reproduction steps, expected impact, and a minimal example where possible. Remove unrelated personal data and secrets. If you have exposed a credential, revoke it rather than relying on deletion of the report.

Supported versions

Security fixes target the latest release. Older versions may require an upgrade; there is no separate long-term support branch or guaranteed response time.

Security model

Gravity launches Claude Code processes with the operating-system permissions of the account running the daemon. Bot directories and permission settings are cooperative boundaries, not an operating-system sandbox. Run only trusted code and review tool permissions before allowing agents access to sensitive resources.

Keep the daemon on a trusted network and use device-scoped tokens for remote clients. Never share the owner token. See the architecture and public-build configuration for authentication, telemetry, and release-signing behavior.

0