PyPI / jsonpath-ng / 1.10.1
jsonpath-ng 1.10.1
- Source
- https://github.com/jsonpath-ng/jsonpath-ng
- Tag scanned
v1.10.1- Compared with
v1.10.0(0 signals introduced since)- Files
- 49 scanned, 8 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 11 info
- Scan time
- 8.3 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 10 of 10 warn and critical signals; 10 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-21 14:56
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
=likely benign PLY lexer uses exec to import a configured lex table module.Reasoning
This is PLY's standard lextab import fallback. The module name comes from the library's own configuration, not untrusted input, and the scanner flagged it only because the exec argument is non-literal.
-
= =likely benign PLY helper reads the caller's module namespace via sys._getframe.Reasoning
sys._getframe with f_globals/f_locals is PLY's standard get_caller_module_dict helper for reading the caller's namespace to build a lexer. The anti-analysis label comes only from the file also containing exec/eval, which PLY needs for its own functionality.
-
= = =likely benign PLY derives a package name and exec-imports it to find the output directory.Reasoning
This is PLY's standard code for importing a package to locate its source directory for output. The package name is derived from the library's own module path, so it is not attacker-controlled.
-
=likely benign PLY uses eval on a grammar literal token string to check its length.Reasoning
PLY evaluates a grammar literal token such as a quoted single character with eval to validate its length. The input is grammar source written by the developer, not runtime or network data.
-
=likely benign PLY yacc uses exec to import a configured parsetab module.Reasoning
This is PLY's standard parsetab import fallback. The module name is configured by the library, so the exec is not an injection vector in this context.
-
= =likely benign PLY helper reads the caller's module namespace via sys._getframe.Reasoning
This is the same standard PLY get_caller_module_dict helper using sys._getframe. The anti-analysis shape is inferred from exec/eval elsewhere in the file, which is normal for PLY.
-
= = =likely benign PLY derives a package name and exec-imports it to locate source files.Reasoning
This matches the standard PLY pattern of importing a package by name to find its source directory. The name comes from the library's module path.
-
=likely benign Generated PLY parser table with a very long line of action data.Reasoning
This is a generated LR parser table with a very long dictionary literal. Long generated tables are expected and contain no executable payload.
-
= -
=likely benign Generated PLY parser table with a long line of action data.Reasoning
This is a generated LR parser table. The long line is ordinary machine-generated data, and the raw-pass long-line signal is a known false-positive shape.
-
= = assertlikely benign Test dynamically imports a generated PLY parsetab module and checks its path.Reasoning
The test imports a module whose name was read from the generated parsetab names and then checks that its file lies inside the package directory. This is a sanity check on the test's own cache, not an injection path, though the dynamic import is a minor concern.
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.
&&