You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f1de919
Browse filesBrowse the repository at this point in the historyBrowse files
feat: justify advisory entry points, keep their conditions and record evidence levels
An advisory now distinguishes the affected_symbols a fix changed from the
public entry_points through which a project reaches them; each entry point
carries the justification tying it to the fix and the conditions under
which it is affected. A condition the engine cannot check is kept on the
finding as pending review, never dropped. modules names what the package
installs, so a required package can be told from an imported one. Every
dependency finding records its evidence level: declared, imported,
reachable or exploitable.
Part of CoreTrace-Entreprise/coretrace-python-analyzer-plugins#2
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,10 @@
2
2
3
3
## Unreleased
4
4
5
+
### Dependencies
6
+
7
+
- Advisories distinguish the `affected_symbols` a fix changed from the public `entry_points` through which they are reached, each justified and carrying `conditions` (checkable argument values, or `semantic` ones kept as pending review); `modules` names what the package installs. Every dependency finding records its evidence `level`: `declared`, `imported`, `reachable` or `exploitable`.
8
+
5
9
### Plugins
6
10
7
11
- Every plugin module is registered in `sys.modules` before it runs, so a single-file plugin may define a dataclass under `from __future__ import annotations` (#105).
0 commit comments