anthropic 1.15.0
- Source
- https://github.com/anthropics/anthropic-sdk-python
- Tag scanned
v1.15.0- Compared with
v1.14.0(0 signals introduced since)- Files
- 2644 scanned, 32 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 6 info
- Scan time
- 8.3 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 5 of 5 warn and critical signals; 5 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 05:48
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
- -
# dont_inherit: this module's `from __future__ import annotations` would turn the annotations into strings. =likely benign Test helper that execs a compiled provider source string into a namespace to build a TokenCache for testing.Reasoning
The exec call sits in a test helper, and the comment explains that dont_inherit is needed so this module's `from __future__ import annotations` does not turn the provider's annotations into strings. That is a deliberate way to build test fixtures from source text. The snippet does not show where the source string comes from, which is the one open question, but nothing here suggests attacker-controlled input or concealment.
-
# dont_inherit: this module's `from __future__ import annotations` would turn the annotations into strings. =likely benign compile call building the code object for the test provider exec above.Reasoning
This compile call is the first half of the same exec(compile(...)) pattern. The dont_inherit flag and the explanatory comment show it is intentional test scaffolding about annotation evaluation, not obfuscation.
-
= assert is not Nonelikely benign Test utility reading the call-stack frame to determine the caller's name.Reasoning
inspect.currentframe is used to find the caller's name for a stacklevel-based helper in test utilities. This is a common, legitimate introspection technique for logging or test labelling and has no evasion or malicious role.
-
# dont_inherit: this module's `from __future__ import annotations` would turn the annotations into strings. =likely benign Test code that execs a function source string to check signature extraction without evaluating annotations.Reasoning
This matches the same test pattern: exec of compiled source with dont_inherit, documented in the comment, to produce a function whose annotations are then inspected by signature_without_evaluating_annotations. It exercises reflection behaviour and is not a dropper.
-
# dont_inherit: this module's `from __future__ import annotations` would turn the annotations into strings. =likely benign compile call producing the code object for the reflection test function exec.Reasoning
The compile call is the other half of the exec(compile(...)) fixture pattern in a reflection test, with the same documented reason for dont_inherit. No sign of hidden payload or runtime fetch appears in the snippet.
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.
&&