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: explain pull request labels in agent instructions (#1521)
mldangelo-oaif95a3f7b3379
diff --git a/AGENTS.md b/AGENTS.mdindex 2db86f022..76321d0fc 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -78,6 +78,32 @@ variables, and defaults as public API.- Update relevant help, schemas, documentation, and tests in the same change.Describe the public CLI change in the pull request.+## Pull request labels++- Use existing labels only when they convey release behavior, dependency updates,+ material platform impact, or actionable maintainer triage. Labels are not+ required to open, test, review, or merge a pull request.+- Start with an accurate Conventional Commit title. For PRs targeting `main`,+ let `node-release-labels` assign the release category: `feat` → `enhancement`,+ `fix` → `bug`, `docs` → `documentation`, and `test`, `release`, or+ `chore(release)` → `skip-release-notes`. A `!` takes precedence and selects+ `breaking-change`. Other types, including ordinary `chore`, have no automatic+ category. Follow the same mapping when manual assignment is needed.+- Preserve maintainer overrides, including manually assigned release labels.+ Do not replace them based only on the title. Use `breaking-change` for an+ actual compatibility break; under the current pre-1.0 policy it causes a minor+ version bump. Use `skip-release-notes` for internal changes that do not affect+ package users; it hides release notes without removing version impact. See+ [RELEASING.md](RELEASING.md) for the full semantics.+- Use `dependencies` for dependency updates across package ecosystems, without+ adding language or ecosystem labels. Use `platform:windows` only when+ Windows-specific behavior is material to the change.+- Do not apply `area:*` labels to PRs. Describe affected surfaces in the title+ and description; leave issue labels and repository label definitions intact.+- Retain existing maintainer triage labels while they identify actionable,+ unresolved work. Do not create new label taxonomies or bulk-edit labels on+ other PRs unless the user asks.+## Public repository and pull requestsEverything published in this repository is public. Review branch names before