Repository navigation
docs(security): inherit organization security policy - #1295
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. |
There was a problem hiding this comment.
π‘ Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8258e532d9
βΉοΈ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with π.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # Security Policy | ||
|
|
||
| Please refer to https://oxc.rs/docs/contribute/security.html for our established security practices. |
There was a problem hiding this comment.
Add the organization policy before deleting this one
At review time, the public oxc-project/.github repository contains no SECURITY.md in its root, .github, or docs directory, so there is no default policy for this repository to inherit under GitHub's community-health inheritance rules. If this deletion lands first, the Security page loses the established-practices and Tidelift reporting instructions; private vulnerability reporting is separate from SECURITY.md and does not provide the claimed shared policy. Add the organization-level file before removing this repository-level policy, or retain this file.
Useful? React with πΒ / π.
Use the shared organization security policy and GitHub private vulnerability reporting, replacing the repository-specific policy.
AI-assisted.