fastmcp 4.1.2
- Source
- https://github.com/PrefectHQ/fastmcp
- Tag scanned
v4.1.2- Compared with
v4.1.1(3 signals introduced since)- Files
- 1019 scanned, 750 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 28 info
- Scan time
- 22.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:26
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewencoding-base64tests/server/auth/test_private_key_jwt_auth.py:144:21new in this release# Non-object headers must fail before reaching JWKS key selection. , ,likely benign Crafted malformed JWT assertion strings used as negative test cases.Reasoning
Malformed JWT-like strings deliberately constructed as negative test inputs for private_key_jwt assertion parsing; base64-like fragments are expected.
-
info
warn→ info by reviewencoding-base64tests/server/auth/test_private_key_jwt_auth.py:145:18new in this release, , , ],likely benign Malformed JWT test fixture string in auth negative test list.Reasoning
Same deliberately malformed JWT test fixture list; no executable or hidden payload.
-
info
warn→ info by reviewencoding-base64tests/server/auth/test_private_key_jwt_auth.py:146:30new in this release, , ], )likely benign Malformed JWT test fixture string in auth negative test list.Reasoning
Same malformed JWT fixture set used in auth tests; benign test data.
-
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 first frame outside the package root.Reasoning
sys._getframe(1) is used to walk up the call stack and find the first caller outside the package, which is a common way to attribute a client inference call to its origin. It is introspection, not execution or exfiltration, and the snippet shows nothing hidden.
-
# Generated code should compilelikely benign Test-only syntax check that compiles generated CLI source without executing it.Reasoning
compile() on generated source only checks syntax and does not execute it. It sits in a test asserting that generated code is valid, so this is a legitimate test pattern.
-
assert not inlikely benign Test-only compile of generated source to verify it is syntactically valid.Reasoning
compile() on generated source in a test only validates syntax; the code is never run. The surrounding asserts confirm this is a test of code generation output.
-
assert inlikely benign Test-only compile check on generated source content.Reasoning
compile() is used as a syntax validity check on generated code in a test, with assertions on the generated text. Compile alone does not execute the code.
-
)likely benign Test-only compile of generated code to check it parses.Reasoning
compile() on generated source in a test to confirm the output parses. No execution occurs, so there is no dynamic-execution risk.
-
assert inlikely benign Test-only syntax validation of generated source.Reasoning
compile() validates generated source as a syntax check inside a test function. The code is not executed.
-
)likely benign Test-only compile of generated script to verify validity.Reasoning
compile() of generated script within a test checks that it is valid Python. It is a standard pattern for testing code generators.
-
) assert inlikely benign Test-only compile check on a generated script.Reasoning
compile() on generated script in a test, followed by assertions on its contents. Compilation without execution is benign.
-
# Should compile without syntax errors # App name should have escaped quotes assert r inlikely benign Test-only compile verifying escaped-quote generated output parses.Reasoning
compile() validates that generated script with escaped quotes is syntactically correct, and assertions follow. This is a test of escaping behavior.
-
)likely benign Test-only syntax check on generated script within a parametrized test.Reasoning
compile() on generated script in a parametrized test is a syntax check on code generator output. No execution occurs.
-
)likely benign Test-only compile of generated script to verify validity.Reasoning
compile() on generated script in a test verifies syntactic validity. Nothing is executed.
-
=likely benign Test-only compile of a generated output file to check syntax.Reasoning
compile() of a generated output file read from disk in a test, used only as a syntax check. No execution follows.
-
= assert in =likely benign Test-only compile of generated script output, followed by content assertions.Reasoning
compile() on generated script read from a test output file, with unicode content assertions. This is a syntax and content check only.
-
)likely benign Base64-encoded PNG image bytes embedded as a test fixture in a conformance server.Reasoning
The blob decodes to a PNG header (iVBORw0KGgo...), a small test image embedded in a conformance server. Base64 image data in a test fixture is expected and is not an obfuscated payload.
-
likely benign Test harness importing modules named in documentation examples to verify they resolve.
Reasoning
__import__ on alias.name from parsed documentation code checks that documented imports resolve. The module name comes from the docs under test, and the ImportError handling records failures. This is a test harness pattern.
-
=likely benign Test harness dynamically importing from-import modules found in doc examples.Reasoning
__import__ with fromlist on node.module from parsed doc examples checks that documented from-imports are valid. It is test-only, and failures are collected rather than hidden.
-
: = returnlikely benign Test helper executes doc example code extracted from markdown.Reasoning
exec of compiled source extracted from documentation code blocks in a test; the source comes from repo docs, not untrusted input.
-
: = returnlikely benign Test helper executes code examples extracted from upgrade-guide documentation.Reasoning
exec(compile(...)) of extracted doc code blocks in a test harness; source comes from repository docs, not untrusted input. Typical doc-testing pattern.
-
likely benign Doc-example test runner execs example code from documentation files.
Reasoning
exec of compiled documentation example sources inside a test; the examples are repo-controlled markdown snippets, so dynamic execution is expected for doc verification.
-
likely benign compile() of documentation example source inside the doc-test runner.
Reasoning
Same compile call paired with the exec above; same benign doc-testing context.
-
= =likely benign Embedded base64-encoded 1x1 PNG image used as test data.Reasoning
Base64 PNG constant of a tiny test image decoded for a downstream test server; a standard embedded image fixture, not a payload.
-
return awaitlikely benign Test executes wrapped generated code to validate code-mode transform.Reasoning
exec of a wrapped test program in a namespace for code-mode sandbox tests; the code under test is generated by the test itself.
-
info
warn→ info by reviewdynamic-executiontests/experimental/transforms/test_code_mode_discovery.py:76:9return awaitlikely benign Test execs wrapped code for code-mode discovery validation.Reasoning
Same exec pattern as the sibling code-mode test; test-local code execution for validating a transform.
-
# Create a simple 1x1 white pixel PNG = b returnlikely benign Inline PNG byte literal used as image test data.Reasoning
A bytes literal encoding a 1x1 PNG for an Image test fixture; binary image data in tests is ordinary and not executed or hidden.
-
= =likely benign Data URI containing a tiny PNG used as icon test input.Reasoning
Base64 PNG data URI used as icon input for an inspect-icons test; standard test fixture.
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.
&&