OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security
TypeScript ai-securityapplication-securityclicode-scanningcodexcodex-securitycybersecuritydevsecopsnodejsnpmopenaisdksecuritytypescriptvulnerability-scanning
docs: add public pull request disclosure safeguards (#384)
Kyle Browncc9ee3df20a5
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.mdnew file mode 100644index 000000000..7480d0257--- /dev/null+++ b/.github/PULL_REQUEST_TEMPLATE.md@@ -0,0 +1,23 @@+## Summary++<!-- Describe the technical problem and outcome without identifying customers or private systems. -->++## Changes++<!-- Summarize the specific changes that reviewers should understand. -->++## Testing++<!-- List the checks you actually ran and their results, or explain why testing was unnecessary. -->++## Risk and rollout++<!-- Describe compatibility, security, operational, or release considerations. -->++## Public disclosure review++<!-- Review every public artifact before checking all three attestations. -->++- [ ] No customer, partner, prospect, or user identities, data, or identifying details are included.+- [ ] No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.+- [ ] I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.diff --git a/AGENTS.md b/AGENTS.mdindex 2a661dcd4..e21938d64 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -13,3 +13,31 @@ Codex Security is a thin wrapper around Codex and its security plugin.- Mention another `openai/` repository in comments or pull request descriptionsonly after checking that it is public. If you cannot confirm its visibility,leave it out.++## Public repository and pull requests++Everything published in this repository is public. Review branch names before+pushing. Before creating or updating a pull request, inspect its branch name,+title, description, commits, changed files, comments, logs, screenshots,+attachments, and links for sensitive information.++- Never identify customers, partners, prospects, or users. Remove names,+ domains, repository URLs, account or tenant identifiers, support cases,+ incidents, and environment details that could identify them.+- Never publish credentials, personal data, private source or configuration,+ scan targets or findings, undisclosed vulnerabilities, or nonpublic links,+ documents, conversations, or issue identifiers.+- Describe the technical behavior generically. Use synthetic names,+ repositories, fixtures, identifiers, logs, and credentials in examples and+ tests.+- Start from `.github/PULL_REQUEST_TEMPLATE.md`, complete every section, report+ the checks you actually ran, and check every disclosure attestation only+ after reviewing the entire pull request.+- Do not use `gh pr create --fill` or `--fill-verbose`: commit messages can+ expose private context. Use a reviewed title and body or+ `gh pr create --template .github/PULL_REQUEST_TEMPLATE.md`.+- Bots and automation are not exempt. Review generated content before+ publication when possible; maintainers must review and correct existing bot+ pull requests before merging them.+- Review material before publishing it. Editing or deleting it afterward does+ not guarantee removal from notifications, caches, or public history.