Repository navigation
docs: align repository security and contributor guidance - #4962
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
HAYDEN-OAI
left a comment
There was a problem hiding this comment.
Retrospective review of 3828825 (this PR merged while the requested review was pending). No substantive introduced issues found across the complete three-file diff.
Checked the private-reporting route, package and repository scope, SDK-owned trust boundaries, contributor/agent guidance, and release-policy wording against the existing release procedure and shared SDK security requirements. The new text preserves repository-specific protections and distinguishes required controls from verified configuration; it does not claim that documentation establishes compliance or clears findings.
Static review only. Tests, lint, CI status, coverage, and mergeability were not run or assessed.
Summary
The repository's security policy only linked the general disclosure policy, and it had no local contributor guide. Expand
SECURITY.md, addCONTRIBUTING.md, and add an agent security checklist inAGENTS.mdto cover repository scope, private sanitized reporting, secrets, dependencies, CI, and publishing.The guidance distinguishes policy requirements from verified operational controls and preserves existing development and release procedures. This change is limited to the three documentation files.
Test plan
git diff --check.Issue number
None.
Checks
.agents/skills/code-change-verification/scripts/run.sh— not applicable to repository-meta-only changes underAGENTS.md.