Skip to content

Commit bd1e45e

Browse files
committed
fix
1 parent ab9b32e commit bd1e45e

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

security/threatmodel.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,14 @@ Every high-quality threat model starts with a clearly defined scope.
66

77
This helps establish a clean separation between **Python-specific security threats** (those tied to the language, its standard library, or common Python idioms) and **general threats** (those that could affect software regardless of implementation language).
88

9-
**Scope**:
9+
**In Scope**:
1010
This threat model covers **a software program written in Python**.
1111

1212
The Python program may provide functionality in one or both of the following ways:
1313
- indirectly, by offering reusable components to other Python programs (as a **module**, **library**, **framework**, or similar), or
1414
- directly, by delivering end-user functionality (CLI tool, GUI application, web service, script, etc.).
1515

1616
This scope intentionally excludes:
17-
- pure Python applications that are merely *consumers* of other libraries/frameworks (unless the consumer introduces novel attack surfaces relevant to Python),
1817
- non-Python components or ecosystems (C extensions are considered only to the extent that they interact with the Python layer in a security-relevant way).
1918

2019

0 commit comments

Comments
 (0)