fastmcp 4.1.3
- Source
- https://github.com/PrefectHQ/fastmcp
- Tag scanned
v4.1.3- Compared with
v4.1.2(0 signals introduced since)- Files
- 1025 scanned, 752 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 28 info
- Scan time
- 16.9 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 28 of 28 warn and critical signals; 28 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-21 05:27
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewframe-introspectionfastmcp_slim/fastmcp/client/transports/inference.py:41:13= 1 =likely benign Walks the call stack via sys._getframe to locate the external caller's filename.Reasoning
sys._getframe walking the call stack to find the first caller outside the package root is a common, legitimate technique for inferring the calling module in a client transport. No network, exec, or obfuscation involved.
-
# Generated code should compilelikely benign Test compiles generated CLI source to check for syntax errors.Reasoning
compile() is applied to generated source code in a test to verify it has valid syntax. It is compile-only (not exec), operating on test-generated strings, so this is a legitimate syntax check.
-
assert not inlikely benign Test compiles generated CLI source to verify syntax.Reasoning
Same pattern: compile-only syntax validation of generated code within a unit test.
-
assert inlikely benign Test compiles generated CLI source for syntax validation.Reasoning
Compile-only syntax check of generated code in a test; no execution.
-
)likely benign Test compiles generated CLI source for syntax validation.Reasoning
Compile-only syntax check of generated code in a test; no execution.
-
assert inlikely benign Test compiles generated CLI source for syntax validation.Reasoning
Compile-only syntax check of generated code in a test; no execution.
-
)likely benign Test compiles generated script to verify it is valid Python.Reasoning
Compile of generated script string in a test to ensure validity; compile alone does not run code.
-
) assert inlikely benign Test compiles generated script for syntax validity.Reasoning
Compile-only validation of generated script in a test.
-
# Should compile without syntax errors # App name should have escaped quotes assert r inlikely benign Test compiles generated script to check escaped-quote handling.Reasoning
Compile-only validation of generated script with escaped quotes; test-only.
-
)likely benign Test compiles generated script for syntax validity.Reasoning
Compile-only validation of generated script in a test.
-
)likely benign Test compiles generated script for syntax validity.Reasoning
Compile-only validation of generated script in a test.
-
=likely benign Test compiles generated output file to verify syntax.Reasoning
Compile-only check of a generated output file read from tmp_path in a test.
-
= assert in =likely benign Test compiles generated output file to verify syntax.Reasoning
Compile-only check of generated output in a test; the string literal includes a non-ASCII arrow and degree sign, which is just test content.
-
)likely benign Base64-encoded PNG image bytes in a conformance test server.Reasoning
The string is a PNG image header (iVBORw0KGgo... with IHDR/IDAT/IEND markers) encoded as base64 for a conformance test fixture. Standard embedded image data, not a payload.
-
likely benign Test attempts to import module names parsed from documentation examples to validate them.
Reasoning
__import__ is used to check whether modules imported in documentation examples are importable, with the module name taken from parsed AST import nodes of doc files. This is a test verifying doc accuracy, not malicious execution, though the dynamic name is a minor smell.
-
=likely benign Test dynamically imports modules referenced in doc examples to catch broken imports.Reasoning
Dynamic __import__ of node.module from parsed doc-example ImportFrom nodes, collecting ImportError failures; a doc validation test, with the module name coming from the repo's own docs.
-
: = returnlikely benign Test harness executes code examples extracted from upgrade docs.Reasoning
exec of compiled source extracted from documentation code blocks in the repo's own test suite. Dynamic execution is the purpose of a doc-example test harness; the source comes from local markdown files, not from untrusted input.
-
: = returnlikely benign compile() of doc-extracted example source feeding the exec call above.Reasoning
compile of the same doc-extracted source; part of the same benign doc-test harness.
-
likely benign Test executes upgrade-guide example code blocks.
Reasoning
Executes documentation examples in a test with warnings suppressed; a standard doc-testing pattern operating on repo files.
-
likely benign compile() of upgrade-guide example source before exec.
Reasoning
compile of the example source in the same doc-test harness.
-
= =likely benign Base64-encoded tiny PNG image fixture.Reasoning
Base64 of a small valid 1x1 PNG image used as test fixture data in a test server; the content is a standard tiny image, not a payload.
-
return awaitlikely benign Test executes generated wrapper code in a namespace for code-mode testing.Reasoning
Test helper executes wrapped code that the test itself constructs for code-mode sandbox testing; no external input reaches it.
-
info
warn→ info by reviewdynamic-executiontests/experimental/transforms/test_code_mode_discovery.py:76:9return awaitlikely benign Test executes generated wrapper code for code-mode discovery testing.Reasoning
Same pattern as the sibling test_code_mode helper; a test-local exec of constructed code.
-
# Non-object headers must fail before reaching JWKS key selection. , ,likely benign Malformed JWT test vector strings for auth negative tests.Reasoning
Deliberately malformed JWT-like strings used as negative test cases for private_key_jwt header validation; fragments are short and not a payload.
-
, , , ],likely benign Malformed JWT test vector for auth negative tests.Reasoning
Same set of intentionally invalid JWT test vectors in the parametrized list.
-
, , ], )likely benign Malformed JWT test vector for auth negative tests.Reasoning
Same intentionally malformed JWT test vector list; base64 fragments decode to ordinary JSON-ish headers used for validation tests.
-
# Create a simple 1x1 white pixel PNG = b returnlikely benign Inline bytes literal of a 1x1 PNG for an Image test fixture.Reasoning
A bytes literal encoding a minimal 1x1 PNG built in a test to create an Image object; binary literal of a valid small image is expected here.
-
= =likely benign Data URI of a tiny PNG icon used in a test.Reasoning
Base64 data URI for a tiny PNG used as an icon fixture in an inspection test; standard test data.
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.
&&