networkx 3.7
- Source
- https://github.com/networkx/networkx
- Tag scanned
networkx-3.7- Compared with
networkx-3.6.1(0 signals introduced since)- Files
- 906 scanned, 49 skipped (binary, oversized, or unrecognised)
- Signals
- 1 critical · 0 warn · 12 info
- Scan time
- 10.7 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 10 of 10 warn and critical signals; 9 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 18:37
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
# print(cmd) = # print(result)likely benign A doc-maintenance script runs a shell command built at runtime and reads its output.Reasoning
This is a developer documentation script that shells out with os.popen on a non-literal cmd. The command is probably a fixed grep-like invocation built from repo paths, but the snippet does not show where cmd comes from, so the shell call is not clearly safe.
-
likely benign IPA transcription of a contributor's name in a release notes author list.
Reasoning
The flagged token is part of an IPA phonetic transcription of a Polish-style surname in an author list, a legitimate use of IPA characters in a release note. Raw-pass unicode mixed-script findings are known to be noisy.
-
likely benign Another IPA glyph fragment from the same contributor name transcription.
Reasoning
The fragment 'skʲ' is the same IPA transcription of the author's name, in the same line. It is a legitimate linguistic annotation.
-
-------------------------- : /- -------------------------- -
# Visualize the graph -
, = assert == . assert ==likely benign Test code evaluates a graph-name string to get a graph object for comparison.Reasoning
eval is used in a test to resolve a graph name from parametrized test data. This is a common test-harness pattern and not a payload.
-
info
warn→ info by reviewdynamic-executionnetworkx/algorithms/operators/tests/test_binary.py:23:31, = assert == . assert ==likely benign Test code evaluates a graph-name string to fetch a fixture graph.Reasoning
Same test-harness pattern: eval resolves a graph fixture name from test parameters in a binary operator test.
-
= =likely benign Lazy-import helper inspects the caller's stack frame to record the import site.Reasoning
inspect.stack is used to find the calling frame's module so that lazy imports can report where they were requested. This is a standard technique in lazy-import helpers and not evasion.
-
= -
=likely benign A test executes a source snippet to verify lazy-import attach behaviour.Reasoning
exec runs a test-supplied source string in a local namespace to check lazy attach behaviour. The source is a test fixture, not attacker-controlled input.
-
= f = =likely benign Decorator code compiles and execs a generated wrapper whose signature matches the decorated function.Reasoning
The file imports bz2 and gzip because open_file-style decorators must open compressed files. The compile/exec sequence builds a wrapper function with the decorated function's signature, a known metaprogramming pattern. Co-occurrence with decoder imports does not indicate a multi-stage payload here.
-
= f = =likely benign compile turns the library-generated wrapper source into a code object.Reasoning
compile here builds the generated wrapper source for the argmap decorator. The code string comes from the library's own template, so this is ordinary code generation.
-
= = =likely benign exec runs the library-generated decorator wrapper code.Reasoning
exec runs the compiled code object from the same library-generated wrapper, so the dynamic execution is internal metaprogramming rather than a dropper.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&