fastmcp 3.4.11
- Source
- https://github.com/PrefectHQ/fastmcp
- Tag scanned
v3.4.11- Compared with
v3.4.10(0 signals introduced since)- Files
- 854 scanned, 390 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 18 info
- Scan time
- 15.1 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 18 of 18 warn and critical signals; 18 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-21 05:26
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
# Generated code should compilelikely benign Test asserts that generated Python source compiles.Reasoning
compile() is applied to generated source inside a test to check that it is syntactically valid. The call does not execute the code and has no obfuscation or malicious indicators.
-
assert not inlikely benign Test compiles generated source to check for syntax errors.Reasoning
Same pattern as the other generator tests: compile() checks syntax of generated source in a test. Nothing suggests malicious intent.
-
assert inlikely benign Test compiles generated source to validate syntax.Reasoning
compile() on generated source in a unit test, used only as a syntax check alongside string assertions.
-
)likely benign Test compiles generated source for syntax validation.Reasoning
compile() on generated output in a test; it validates the generator's output and does not execute it.
-
assert inlikely benign Test compiles generated source for syntax validation.Reasoning
compile() on generated output in a test with string assertions. It is a syntax check, not dynamic execution of untrusted input.
-
)likely benign Test compiles a generated script to ensure it is valid.Reasoning
compile() of a generated script inside a test. The result is only checked for syntax errors.
-
) assert inlikely benign Test compiles generated script and asserts on its content.Reasoning
Generated script is compiled in a test and then checked for expected strings. This is ordinary test verification.
-
# Should compile without syntax errors # App name should have escaped quotes assert r inlikely benign Test checks that generated script with escaped quotes compiles.Reasoning
compile() validates that the generated app name with escaped quotes produces valid syntax. This is an expected test for escaping behavior.
-
)likely benign Test compiles generated script for stdio transport.Reasoning
Generated script compile in a stdio transport test. It is a syntax check only.
-
)likely benign Test compiles generated script to verify syntax.Reasoning
Syntax check of generated script in a test. No execution of untrusted content or obfuscation.
-
=likely benign Test compiles generated output file to verify it is valid Python.Reasoning
compile() on the content of an output file the test just generated. It verifies syntax and does not execute the code.
-
)likely benign Embedded base64 PNG image data in a conformance test server.Reasoning
The snippet is a base64 PNG image literal (PNG header and IDAT-like data) in a conformance test server. Raw pass base64 heuristics commonly flag embedded image fixtures. It is not an encoded payload.
-
likely benign Test checks that imports in doc examples resolve, using __import__ on parsed names.
Reasoning
__import__ is called on alias names parsed from documentation code examples to check that they import. The module names come from the repo's own docs inside a test, so this is a verification pattern rather than a dropper.
-
=likely benign Test imports modules referenced in doc examples to validate them.Reasoning
Dynamic import of node.module parsed from doc examples, wrapped in try/except ImportError to collect errors. This is a doc-validation test on repo content.
-
return awaitlikely benign Test executes a wrapped code snippet in an isolated namespace to exercise code mode.Reasoning
exec runs a wrapper built by the test to exercise the code-mode transform. The code is test-authored and the namespace is local. This is expected for testing an execution feature, though exec is inherently sensitive.
-
info
warn→ info by reviewdynamic-executiontests/experimental/transforms/test_code_mode_discovery.py:76:9return awaitlikely benign Test executes a wrapped snippet to exercise code-mode discovery.Reasoning
Same pattern as test_code_mode: exec of a test-constructed wrapper in a local namespace to test discovery behavior. No sign of hidden or malicious payloads.
-
# Create a simple 1x1 white pixel PNG = b returnlikely benign A test fixture embedding a tiny PNG image as a bytes literal.Reasoning
The bytes literal is a genuine 1x1 white PNG file (PNG signature, IHDR, IDAT, IEND chunks), built in a test to exercise Image handling. The escapes are just how raw binary is written in Python source; there is no execution, decoding, or network activity. The comment states its purpose.
-
= =likely benign A base64-encoded PNG data URI used as test input for icon handling.Reasoning
The string is a standard data URI for a tiny PNG image used as a test fixture for a FastMCP server's icon handling. It is only assigned to a variable and passed around as data, not decoded and executed. Base64 image data in tests is ordinary and expected.
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.
&&