fastmcp 3.4.10
- Source
- https://github.com/PrefectHQ/fastmcp
- Tag scanned
v3.4.10- Compared with
v3.4.9(0 signals introduced since)- Files
- 854 scanned, 390 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 18 info
- Scan time
- 14.6 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:25
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 code compiles.Reasoning
compile() is applied to source produced by the code generator under test, as a syntax check. It only compiles and never executes, and this is a test file.
-
assert not inlikely benign Test compiles generated source to check for syntax errors.Reasoning
Same pattern: compile() on generated source as a syntax check inside a test, with no execution.
-
assert inlikely benign Test compiles generated source after asserting on its contents.Reasoning
compile() on generator output in a test; the surrounding asserts check the generated text. Compile-only, no execution.
-
)likely benign Test compiles generated code with a complex type default.Reasoning
compile() on generator output in a unit test as a syntax check. No execution occurs.
-
assert inlikely benign Test compiles generated code for name-collision handling.Reasoning
compile() on generated code in a test, a standard syntax validation step.
-
)likely benign Test compiles generated tool script.Reasoning
compile() on a script produced by the generator under test. Compile-only validation inside a test.
-
) assert inlikely benign Test compiles generated server script.Reasoning
compile() on generated script as a syntax check in a test file, with no execution.
-
# Should compile without syntax errors # App name should have escaped quotes assert r inlikely benign Test checks generated app name escaping compiles.Reasoning
compile() validates generated output containing escaped quotes; no execution, test context.
-
)likely benign Test compiles generated stdio transport script.Reasoning
compile() on generator output in a test for stdio transport. Compile-only.
-
)likely benign Test compiles generated script.Reasoning
compile() on generator output as a syntax check in a test.
-
=likely benign Test compiles generated output file.Reasoning
compile() on generated file contents read back from a test output path. Syntax check only.
-
)likely benign Base64-encoded PNG image literal in a conformance test server.Reasoning
The blob is a base64-encoded 1x1 PNG image constant, a normal test fixture. The payload is a valid image header and is not hiding executable content.
-
likely benign Doc-example test checks that imported modules resolve via __import__.
Reasoning
__import__ is called on module names parsed from the repository's own documentation to check that doc examples import successfully. The inputs are not attacker-controlled and this is a test utility.
-
=likely benign Doc-example test dynamically imports a module named in docs.Reasoning
Dynamic import of a module name taken from repository docs during a test; it only verifies importability and errors are collected.
-
return awaitlikely benign Test executes a wrapped test main function via exec in a namespace.Reasoning
exec runs wrapped code built by the test fixture inside an isolated namespace to exercise the code-mode transform. The code is test-authored, not external input, though exec is a sensitive pattern.
-
info
warn→ info by reviewdynamic-executiontests/experimental/transforms/test_code_mode_discovery.py:76:9return awaitlikely benign Discovery test executes wrapped test code via exec.Reasoning
Same pattern as the sibling code-mode test: exec of test-authored wrapped code in a namespace to exercise discovery behavior.
-
# Create a simple 1x1 white pixel PNG = b returnlikely benign A test fixture embedding a tiny PNG image as a Python bytes literal passed to an Image constructor.Reasoning
The bytes literal is a complete 1x1 white PNG file (PNG signature, IHDR, IDAT, IEND chunks) and the preceding comment says it creates a 1x1 white pixel PNG for an Image test. The escape-heavy form is just how raw binary is written in a Python bytes literal; it is test fixture data with no execution or exfiltration behavior.
-
= =likely benign A test data URI containing a small base64-encoded PNG image for an icon-inspection test.Reasoning
The base64 string is a standard PNG data URI used as a test input for a FastMCP server named DataURIServer. It is a small image payload in a test file, with no decoding into executable content or any suspicious use shown. The raw-pass base64 signal is a known false positive for embedded image 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.
&&