← Back to PRs

#22070: docs: add minimal public safety checklist for template sharing

by MinwooKim1990 open 2026-02-20 17:38 View on GitHub →
docs security scripts size: S
## Why This PR adds a minimal, public-safe security checklist that can be reused by users and contributors without exposing tenant-specific internals. ## What changed - Added docs/security/minimal-public-safety-checklist.md with a compact baseline: - Treat external/fetched input as untrusted - Require explicit approval for destructive actions - Redact output before external publishing - Keep access scoped and reduce blast radius - Linked the checklist from docs/security/README.md - Added a short reference in docs/cli/security.md for public template sharing guidance ## Security philosophy The intent is to encourage safe defaults in community sharing: - Deny-by-default dangerous operations - Require explicit approvals for risky commands - Sanitize before public exposure - Keep private/environment-specific policy values out of open-source artifacts ## Validation - Docs-only change; no runtime behavior change in OpenClaw. - Patch is intentionally minimal to reduce unnecessary attack-surface disclosure while still improving safety clarity. <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds a minimal, public-safe security checklist (`docs/security/minimal-public-safety-checklist.md`) for community template sharing, along with cross-references in the CLI security docs and security README. The checklist provides generic baseline guidance (trust boundaries, approval gates, secret redaction, scoped access) without exposing tenant-specific internals. Documentation follows Mintlify conventions with root-relative links and maintains consistency with existing security documentation tone and structure. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - Documentation-only changes with no runtime behavior modifications. The new content follows established project conventions (Mintlify linking, generic content, appropriate tone), cross-references are valid, and the security guidance is sensible and non-sensitive - No files require special attention <sub>Last reviewed commit: f5a815b</sub> <!-- greptile_other_comments_section --> <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> <!-- /greptile_comment -->

Most Similar PRs