networkx 3.7
- Source
- https://github.com/networkx/networkx
- Artifact scanned
networkx-3.7-py3-none-any.whl- Compared with
networkx-3.6.1-py3-none-any.whl(0 signals introduced since)- Files
- 586 scanned, 18 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 8 info
- Scan time
- 10.0 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 7 of 7 warn and critical signals; 7 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 06:25
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
, = assert == . assert ==likely benign Test assertion that uses eval to look up a named test graph by string.Reasoning
The eval is in a test assertion and evaluates a graph name taken from the test's own fixture dictionary, not external input. This is a test-harness idiom, not a payload.
-
info
warn→ info by reviewdynamic-executionnetworkx/algorithms/operators/tests/test_binary.py:23:31, = assert == . assert ==likely benign Test assertion that uses eval to resolve a named test graph.Reasoning
Same pattern as test_all.py: eval resolves a fixture graph name inside a test assertion. No untrusted input reaches it.
-
= =likely benign Reads the calling frame to record the importing module for lazy loading.Reasoning
inspect.stack()[1] reads the caller's module name so the lazy-import helper can record which module requested the import. This is ordinary introspection for lazy loading and does not execute or hide anything.
-
= -
=likely benign Test that execs generated lazy-import stub source into a local dict and checks the result.Reasoning
This test executes generated stub source in an isolated namespace and checks the resulting attach/lazy names. The input is test-authored code, so the exec is part of verifying lazy-import stub generation.
-
= f = =likely benign Generates a specialized wrapper function from a signature via compile and exec in the argmap decorator.Reasoning
The argmap decorator builds a wrapper function from the decorated function's signature by compiling and exec-ing generated source. The bz2/gzip imports are generic to the module and the source is derived from the decorator's own code, not from a downloaded or encoded payload. The decoder-plus-exec heuristic matches the shape but not the content.
-
= f = =likely benign compile of generated wrapper source inside the argmap decorator.Reasoning
The compile call turns code generated from the decorated function's signature into a code object for the same wrapper. It is part of the code-generation mechanism and carries no sign of a hidden payload.
-
= = =likely benign exec of the compiled wrapper to materialize the decorated function in the argmap decorator.Reasoning
The exec runs the compiled wrapper into controlled namespaces so the decorator can fetch the generated function. This is a known metaprogramming technique for preserving signatures and does not reach the network or decode an opaque blob.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|