chaokunyang commented on code in PR #3734:
URL: https://github.com/apache/fory/pull/3734#discussion_r3418723777


##########
THREAT_MODEL.md:
##########
@@ -0,0 +1,182 @@
+<!--
+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.
+-->
+
+# Apache Fory — Threat Model (v0 draft)
+
+## §1 Header
+
+- **Project:** Apache Fory (`apache/fory`), `main`, against which this draft 
was written. Fory is a multi-language serialization framework (Java, C++, 
Python, Go, Rust, JavaScript, Kotlin, Scala, Swift, Dart, C#).
+- **Date:** 2026-06-02. **Status:** draft — for Apache Fory PMC review. 
**Author:** ASF Security team (drafted via the Scovetta threat-model rubric), 
for PMC ratification.

Review Comment:
   I would not publish this as the linked triage policy while it is still 
framed as an unratified draft. The inferred-claim counts and open maintainer 
questions are useful review material, but once `SECURITY.md` points here, 
reporters and scanners can cite them as project policy. Before this becomes the 
public model, I think we should either remove the 
draft/provenance/open-question scaffolding or keep this as discussion material 
and publish only the ratified, durable boundaries under `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]

Reply via email to