chaokunyang commented on code in PR #3734: URL: https://github.com/apache/fory/pull/3734#discussion_r3418722385
########## SECURITY.md: ########## @@ -0,0 +1,29 @@ +<!-- +SPDX-License-Identifier: Apache-2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + https://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> + +# Security Policy + +## Reporting a Vulnerability + +`apache/fory` follows the [Apache Software Foundation security process](https://www.apache.org/security/). Please report suspected +vulnerabilities privately to `[email protected]`; do not open public +GitHub issues or pull requests for security reports. + +## Threat Model + +What the project treats as in scope and out of scope, the security +properties it provides and disclaims, the adversary model, and how +findings are triaged are documented in [THREAT_MODEL.md](./THREAT_MODEL.md). Review Comment: Since main now has `docs/security/`, I would avoid making a new top-level threat model the only policy link from `SECURITY.md`. Root `SECURITY.md` is the right place for the private reporting channel and GitHub discoverability; the model entry point should be `docs/security/index.md`, with the detailed deserialization rules under `docs/security/deserialization.md`. That keeps scanners and humans on one security-doc hierarchy instead of splitting authority between root and `docs/security`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
